feat: add scalar-only search queries - #15
Merged
Merged
Conversation
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.
The safe wrapper cannot currently construct a scalar-only query, although the native C API supports filtering collections without vector or FTS fields. This prevents consumers such as zvec-grep from checking file metadata through the safe API without a local patch.
Add
SearchQuery::scalar(topk)so callers can apply existing filters and output projections without supplying a vector, FTS payload, or target field. The query owns its native handle before fallible setup, ensuring cleanup on failure. Existing APIs remain unchanged.Add regression coverage for exact and prefix matching, missing matches, field projection, result limits, and the empty-file-name existence query used by zvec-grep. Document the API and its unordered, bounded results in both READMEs.
Validation:
rustfmt --checkandgit diff --checkpassed. Compilation and runtime tests were not run because local repository instructions require an explicit request for those checks.