Hide scaling limit changes

developers/weaviate/config-refs/env-vars.md

@@ -42,8 +42,7 @@ import Link from '@docusaurus/Link';
 | `GRPC_PORT` | The port on which Weaviate's gRPC server listens for incoming requests. Default: `50051` | `string - number` | `50052` |
 | `LIMIT_RESOURCES` | If `true`, Weaviate will automatically attempt to auto-detect and limit the amount of resources (memory & threads) it uses to (0.8 * total memory) and (number of cores-1). It will override any `GOMEMLIMIT` values, however it will respect `GOMAXPROCS` values. | `boolean` | `false` |
 | `LOG_FORMAT` | Set the Weaviate logging format <br/><br/>Default: Outputs log data to json. e.g.: `{"action":"startup","level":"debug","msg":"finished initializing modules","time":"2023-04-12T05:07:43Z"}` <br/>`text`: Outputs log data to a string. e.g. `time="2023-04-12T04:54:23Z" level=debug msg="finished initializing modules" action=startup` | `string` |  |
-| `LOG_LEVEL` | Sets the Weaviate logging level. Default: `info`<br/><br/>`panic`: Panic entries only. (new in `v1.24`) <br/>`fatal`: Fatal entries only. (new in `v1.24`)  <br/> `error`: Error entries only. (new in `v1.24`) <br/>`warning`: Warning entries only. (new in `v1.24`) <br/>`info`: General operational entries. <br/> `debug`: Very verbose logging. <br/>`trace`: Even finer-grained informational events than `debug`. | `string` | |
-| `MAXIMUM_ALLOWED_COLLECTIONS_COUNT` | Maximum allowed number of collections. A value of `-1` removes the limit. (default: `100`) <br/><br/>Instead of raising the collections count limit, consider [rethinking your architecture](/developers/weaviate/starter-guides/managing-collections/collections-scaling-limits).<br/>Added in `v1.25.33`, `v1.26.17`, `1.27.14`, `1.28.8`, `1.29.1`| `string - number` | `20` | 
+| `LOG_LEVEL` | Sets the Weaviate logging level. Default: `info`<br/><br/>`panic`: Panic entries only. (new in `v1.24`) <br/>`fatal`: Fatal entries only. (new in `v1.24`)  <br/> `error`: Error entries only. (new in `v1.24`) <br/>`warning`: Warning entries only. (new in `v1.24`) <br/>`info`: General operational entries. <br/> `debug`: Very verbose logging. <br/>`trace`: Even finer-grained informational events than `debug`. | `string` | | <!--| `MAXIMUM_ALLOWED_COLLECTIONS_COUNT` | Maximum allowed number of collections. A value of `-1` removes the limit. (default: `100`) <br/><br/>Instead of raising the collections count limit, consider [rethinking your architecture](/developers/weaviate/starter-guides/managing-collections/collections-scaling-limits).<br/>Added in `v1.25.33`, `v1.26.17`, `1.27.14`, `1.28.8`, `1.29.1`| `string - number` | `20` | -->
 | `MEMORY_READONLY_PERCENTAGE` | If memory usage is higher than the given percentage all shards on the affected node will be marked as `READONLY`, meaning all future write requests will fail. (Default: `80`) | `string - number` | `75` |
 | `MEMORY_WARNING_PERCENTAGE` | If memory usage is higher than the given percentage a warning will be logged by all shards on the affected node's disk. (Default: `0` - i.e. no limit) | `string - number` | `85` |
 | `MODULES_CLIENT_TIMEOUT` | Timeout for requests to Weaviate modules. Default: `50s` | `string - duration` | `5s`, `10m`, `1h` |

developers/weaviate/config-refs/schema/index.md

@@ -149,7 +149,7 @@ To avoid this, you can either:
 - Delete the collection, re-create it with the new property and then re-import the data.
 
 We are working on a re-indexing API to allow you to re-index the data after adding a property. This will be available in a future release.
-
+<!--
 ### Collections count limit {#collections-count-limit}
 
 :::info
@@ -169,7 +169,7 @@ This change does not affect existing clusters that have already exceeded the def
 **Instead of raising the collections count limit, consider rethinking your architecture**.  
 For more details, see [Starter Guides: Scaling limits with collections](/developers/weaviate/starter-guides/managing-collections/collections-scaling-limits). 
 :::
-
+-->
 ## Available parameters
 
 ### `class`

developers/weaviate/manage-data/collections.mdx

@@ -90,11 +90,11 @@ Using too many collections can lead to scalability issues like high memory usage
 
 For more details, see [Starter Guides: Scaling limits with collections](/developers/weaviate/starter-guides/managing-collections/collections-scaling-limits).
 :::
-
+<!--
 import CollectionsCountLimit from '/_includes/collections-count-limit.mdx'
 
 <CollectionsCountLimit />
-
+-->
 ## Create a collection and define properties
 
 Properties are the data fields in your collection. Each property has a name and a data type.

developers/weaviate/starter-guides/managing-collections/collections-scaling-limits.mdx

@@ -6,8 +6,8 @@ image: og/docs/more-resources.jpg
 # tags: ['performance']
 ---
 
-:::info
-Added in `v1.25.34`, `v1.26.18`, `1.27.15`, `1.28.9`, `1.29.2`
+:::caution 🚧 Under construction 🚧 
+**The collection count limit will be introduced in the near future.**
 :::
 
 :::caution You hit the collections count limit?