From c7e2f8a98c089f695a63f40f625237e50549bfe4 Mon Sep 17 00:00:00 2001 From: Abdon Pijpelink Date: Fri, 24 Apr 2026 09:56:39 +0200 Subject: [PATCH] Clarify default wait behavior with prevent_unoptimized (#2302) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Clarify default wait behavior with prevent_unoptimized * Update qdrant-landing/content/documentation/ops-optimization/optimizer.md Co-authored-by: Tim Visée --------- Co-authored-by: Tim Visée --- .../content/documentation/ops-optimization/optimizer.md | 6 ++++-- .../content/documentation/search/low-latency-search.md | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/qdrant-landing/content/documentation/ops-optimization/optimizer.md b/qdrant-landing/content/documentation/ops-optimization/optimizer.md index 58ddb6ecc..d5e88caae 100644 --- a/qdrant-landing/content/documentation/ops-optimization/optimizer.md +++ b/qdrant-landing/content/documentation/ops-optimization/optimizer.md @@ -140,14 +140,16 @@ To mitigate this, Qdrant supports a `prevent_unoptimized` mode. When enabled, po {{< code-snippet path="/documentation/headless/snippets/update-collection/prevent-unoptimized/" >}} With `prevent_unoptimized` enabled, setting `indexed_only` to `true` is not necessary. They are mutually exclusive. ### Effect on `wait=true` -Write requests support a [`wait` parameter](/documentation/manage-data/points/#awaiting-result) that, when set to `true`, causes the request to return only after the update has been applied and is visible for search. With `prevent_unoptimized` enabled, setting `wait=true` is not recommended without understanding the implications. +Write requests support a [`wait` parameter](/documentation/manage-data/points/#awaiting-result) that, when set to `true`, causes the request to return only after the update has been applied and is visible for search. If `prevent_unoptimized` is enabled, `wait` should be set to `false` to avoid potential timeouts and delays. + +This is particularly important for the Python, TypeScript/JavaScript, .NET, and Java clients, that set `wait` to `true` by default. The Go and Rust clients and the REST API interface already default to `false`, so no change is needed when using those clients. Qdrant processes updates in strict order: each update is written to the write-ahead log and then applied sequentially by the update worker, preserving this order. diff --git a/qdrant-landing/content/documentation/search/low-latency-search.md b/qdrant-landing/content/documentation/search/low-latency-search.md index 9bf18bfbe..91370cbc7 100644 --- a/qdrant-landing/content/documentation/search/low-latency-search.md +++ b/qdrant-landing/content/documentation/search/low-latency-search.md @@ -66,5 +66,5 @@ To mitigate "blinking" points, an alternative to using `indexed_only` is to set Refer to [Prevent Reads from Large Unindexed Segments](/documentation/ops-optimization/optimizer/#prevent-reads-from-large-unindexed-segments) for more details on how this works. \ No newline at end of file