From c9d6fc43a6591159810e10131592b18ae03d8dfd Mon Sep 17 00:00:00 2001 From: QianZhu Date: Wed, 12 Mar 2025 09:31:09 -0700 Subject: [PATCH] docs: use bypass_vector_index() instead of use_index=false (#2115) --- docs/src/sql.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/sql.md b/docs/src/sql.md index f05a0d62..41b44491 100644 --- a/docs/src/sql.md +++ b/docs/src/sql.md @@ -7,7 +7,7 @@ performed on the top-k results returned by the vector search. However, pre-filte option that performs the filter prior to vector search. This can be useful to narrow down the search space of a very large dataset to reduce query latency. -Note that both pre-filtering and post-filtering can yield false positives. For pre-filtering, if the filter is too selective, it might eliminate relevant items that the vector search would have otherwise identified as a good match. In this case, increasing `nprobes` parameter will help reduce such false positives. It is recommended to set `use_index=false` if you know that the filter is highly selective. +Note that both pre-filtering and post-filtering can yield false positives. For pre-filtering, if the filter is too selective, it might eliminate relevant items that the vector search would have otherwise identified as a good match. In this case, increasing `nprobes` parameter will help reduce such false positives. It is recommended to call `bypass_vector_index()` if you know that the filter is highly selective. Similarly, a highly selective post-filter can lead to false positives. Increasing both `nprobes` and `refine_factor` can mitigate this issue. When deciding between pre-filtering and post-filtering, pre-filtering is generally the safer choice if you're uncertain.