Draft
Conversation
Fixes GitHub issue #337 by allowing queries with only sparseVector parameter, enabling cascading retrieval patterns with separate dense and sparse indexes. Changes: - Add new QueryBySparseVector type for sparse-only queries - Update QueryOptions union to include QueryBySparseVector - Update validator to require at least one of: id, vector, or sparseVector - Allow empty vector when sparseVector is provided - Export QueryBySparseVector type from main index files - Add comprehensive tests for sparse-only query scenarios All tests pass and TypeScript compilation succeeds.
|
Cursor Agent can help with this pull request. Just |
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
2 participants
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.
Add support for sparse-only queries to enable cascading retrieval patterns and align the SDK's
QueryOptionstype with the backend API.Linear Issue: PIN-43