Bump all SDK versions to latest and update vector search page#251
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
# Conflicts: # docs/search/vector-search.mdx
prrao87
changed the title
…and Rust Replace the hardcoded code blocks on the vector search page with snippets generated from the language test suites, so every example shown is actually compiled/executed and stays in sync with the SDKs. - Add Python and TypeScript test coverage for the full set of vector search operations: distance-metric configuration, nested vector-column selection and indexing, exact-vs-approximate distances, pre- and post-filtering, batch search, distance-range search, binary (hamming) search, brute-force search, bypassing the index, and fast search. Expensive steps such as Hugging Face dataset loads are mocked so the suite stays fast and offline. - Add a Rust example covering the search variants the Rust SDK supports, including batch (multi-query) and binary/hamming search. - Upgrade the TypeScript and Rust SDKs to the latest release and migrate the example suite to the new APIs: wrapping record-batch readers for table creation, the relocated namespace request types, and the newer Arrow version. - Drop connection setup from the vector search snippets; they now assume the caller already has an open connection rather than hardcoding one. Note: late-interaction multivector search stays Python/TypeScript only, since the Rust SDK does not yet expose a single-matrix query API. Co-Authored-By: Claude Opus 4.7 <[email protected]>
…/129b42b9 # Conflicts: # docs/search/vector-search.mdx
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
1 participant
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
Document the new behavior where LanceDB automatically discovers a single vector column nested inside a struct when running searches or creating an index.
Changes
Context
Follows the upstream change that recurses into struct fields when resolving the default vector column, so users with a single nested vector leaf no longer need to pass an explicit field path.
Additional Updates
This PR also makes the vector search documentation fully testable: every code example on the page is now generated from the language test suites (Python, TypeScript, Rust) instead of being hardcoded, so examples are compiled/executed in CI and stay in sync with the SDKs. Also bumps the TypeScript and Rust SDKs to the latest release and migrates the example suite to the new APIs.
Key updates
Testing
Notes