From c4745e5891cd83cb0a5127ffb2b410f33ee69427 Mon Sep 17 00:00:00 2001 From: David Myriel Date: Wed, 30 Apr 2025 17:42:22 +0200 Subject: [PATCH] Update qdrant-landing/content/articles/vector-search-production.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Tim Visée --- qdrant-landing/content/articles/vector-search-production.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/articles/vector-search-production.md b/qdrant-landing/content/articles/vector-search-production.md index 8c27a9e3a..2165cca71 100644 --- a/qdrant-landing/content/articles/vector-search-production.md +++ b/qdrant-landing/content/articles/vector-search-production.md @@ -162,7 +162,7 @@ Once all records are inserted, you can rebuild the index in a single pass. Consi > It's possible for indexing to temporarily fall behind data ingestion, both during gradual streaming uploads and after large bulk uploads. -By default, searches include indexed data. However, a large number of unindexed points can significantly slow down searches due to full scans, potentially causing high search latency, timeouts, and application failures. +By default, searches include unindexed data. However, a large number of unindexed points can significantly slow down searches due to full scans, potentially causing high search latency, timeouts, and application failures. If the maximum number of indexed points remains consistently low, this is likely not an issue. If you anticipate periods with many unindexed points, you should take measures to prevent search disruptions in production.