krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-10-07 11:58:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

Mark prevent_unoptimized as experimental (#2202)

Browse Source 
* Mark prevent_unoptimized as experimental

* Update qdrant-landing/content/documentation/guides/low-latency-search.md

Co-authored-by: Tim Visée <tim@visee.me>

---------

Co-authored-by: Tim Visée <tim@visee.me>
This commit is contained in:
Abdon Pijpelink
2026-03-13 16:16:07 +01:00
committed by GitHub
co-authored by Tim Visée
parent 9bf4f6d126
commit 456e01b514
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/guides/low-latency-search.md
+3 -1
View File
@@ -47,4 +47,6 @@ Search latency can vary depending on where the data is in this process. Querying
If your application requires a consistently low search latency, set the [search parameter](/documentation/concepts/search/#search-api) `indexed_only` to `true`. With this setting enabled, search operations will only consider indexed data, ensuring more consistent and lower response times. The tradeoff is that the most recent data might not be included in search results until it has been indexed.
Enabling `indexed_only` can cause recently updated data to temporarily disappear from search results until it is indexed again. To mitigate this, set the `prevent_unoptimized` optimizer setting to `true` when [creating or updating a collection](/documentation/concepts/collections/#update-collection-parameters), or globally in the [configuration file](/documentation/concepts/optimizer/). This prevents the creation of large unoptimized segments by throttling updates from the update queue to match the indexing rate.
Enabling `indexed_only` can cause recently updated data to temporarily disappear from search results until it is indexed again. To mitigate this, set the `prevent_unoptimized` optimizer setting to `true` when [creating or updating a collection](/documentation/concepts/collections/#update-collection-parameters), or globally in the [configuration file](/documentation/concepts/optimizer/). This prevents the creation of large unoptimized segments by throttling updates from the update queue to match the indexing rate.
<aside role="alert"><code>prevent_unoptimized</code> is an experimental feature; its behavior may change in future releases and it is not recommended for production use yet.</aside>