Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Close five gaps surfaced by the docs-audit run on the search area, all grounded in the lancedb OSS source and Enterprise serving layer:
optimize(), the unindexed-tail flat-scan fallback, andfast_search(). Reuses the existingPyFtsIncrementalIndexsnippet.with_row_id/withRowId,distance_range/distanceRange, and prefilter vs. postfilter. Verified againstLanceHybridQueryBuilder._create_query_buildersand TSQueryBase.rows × vectors-per-row, that LanceDB Enterprise applies a ~10× stricter brute-force KNN threshold for multivector columns (per sophon'sMULTI_VECTOR_ROW_MULTIPLIER), and that OSS has no equivalent guard. The ColBERT example now builds the index instead of skipping it.explain_plan/analyze_planon FTS and hybrid queries, including the reranker-label + sub-plan format hybrid emits.EXPLAIN/EXPLAIN ANALYZE/EXPLAIN VERBOSEover the FlightSQL endpoint, with a pointer back to the optimize page.No new tests or snippet regeneration needed — the only snippet import added (
PyFtsIncrementalIndex) was already generated.Test plan
/search/optimize-queries#analyzing-non-vector-queriesresolves fromhybrid-search.mdx