From f9ccefb0320574262dd88c2923ed25171996a181 Mon Sep 17 00:00:00 2001 From: Will Jones Date: Fri, 13 Oct 2023 11:17:10 -0700 Subject: [PATCH] feat: expose use_index in LanceDB OSS --- docs/src/search.md | 4 ++++ node/src/query.ts | 16 ++++++++++++++++ node/src/test/test.ts | 15 +++++++++++++++ python/lancedb/query.py | 19 +++++++++++++++++++ python/lancedb/remote/table.py | 4 ++++ python/lancedb/table.py | 4 +++- python/tests/test_query.py | 5 ++++- rust/ffi/node/src/query.rs | 7 ++++++- 8 files changed, 71 insertions(+), 3 deletions(-) diff --git a/docs/src/search.md b/docs/src/search.md index 5a3143fe..eb08f40d 100644 --- a/docs/src/search.md +++ b/docs/src/search.md @@ -27,6 +27,8 @@ Currently, we support the following metrics: If you do not create a vector index, LanceDB would need to exhaustively scan the entire vector column (via `Flat Search`) and compute the distance for *every* vector in order to find the closest matches. This is effectively a KNN search. +(Even if you create a vector index, you can force this behavior in LanceDB OSS by setting `use_index=False`, +as shown below.)