From 1087baaa89570515ca27dc66cd62d1b1ff102b62 Mon Sep 17 00:00:00 2001 From: timvisee Date: Fri, 17 Jan 2025 11:44:58 +0100 Subject: [PATCH] Interlink collection create and update operations --- .../content/documentation/concepts/collections.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/qdrant-landing/content/documentation/concepts/collections.md b/qdrant-landing/content/documentation/concepts/collections.md index fe9ac19c1..41ea47178 100644 --- a/qdrant-landing/content/documentation/concepts/collections.md +++ b/qdrant-landing/content/documentation/concepts/collections.md @@ -778,7 +778,7 @@ Upon crossing a limit, the server will return a client side error with the infor As part of the config, the `enabled` field act as a toggle to enable or disable the strict mode dynamically. -The `strict_mode_config` can be enabled when creating a collection, for instance below to active the `unindexed_filtering_retrieve` limit. +The `strict_mode_config` can be enabled when [creating](#create-a-collection) a collection, for instance below to active the `unindexed_filtering_retrieve` limit. ```http PUT /collections/{collection_name} @@ -891,7 +891,7 @@ client.CreateCollection(context.Background(), &qdrant.CreateCollection{ }) ``` -or enabled later on an existing collection. +Or enable it later on an existing collection through the [collection update](#update-collection-parameters) API: ```http PATCH /collections/{collection_name} @@ -996,7 +996,7 @@ client.UpdateCollection(context.Background(), &qdrant.UpdateCollection{ }) ``` -It can be disabled on an existing collection. +To disable strict mode on an existing collection use: ```http PATCH /collections/{collection_name}