[python] Add search result scores and explicit relevance ordering - #10005
Open
TheR1sing3un wants to merge 1 commit into
Open
TheR1sing3un wants to merge 1 commit into
TheR1sing3un wants to merge 1 commit into
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
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.
Purpose
Multimodal search currently returns projected rows without exposing their relevance scores, and final lookup determines the output order. Add opt-in
with_score(column_name="_score")andorder_by_score()for data-evolution tables, including full-text/hybrid queries and local/Ray single and batch vector queries. Scores retain the existing higher-is-better convention; ordering uses descending score and ascending row ID for ties.Queries explicitly selecting only row IDs or scores can skip final lookup when neither a post-filter nor query authorization requires it. Batch queries retain their shared lookup and attach scores separately for each query. Existing queries keep their default behavior. Document score meanings and the scope of the lookup optimization.
Related to #8484.
Tests