Relate labeled() to equivalent operators in other search engines - #4844
Merged
Conversation
Add a short note to the labeled() reference documentation pointing out that it plays the same role as Lucene's ConstantScoreQuery, reached via function_score in Elasticsearch/OpenSearch and via the ^= syntax in Solr. Why: users migrating from those engines look for a way to attach a fixed score contribution to a sub-query without letting it affect matching. Naming the operator they already know makes labeled() discoverable from that starting point, instead of leaving them to infer the mapping from the Vespa-specific description of labels and itemRawScore.
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
3 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 a short note to the labeled() reference documentation pointing out that it plays the same role as Lucene's ConstantScoreQuery, reached via function_score in Elasticsearch/OpenSearch and via the ^= syntax in Solr.
Why: users migrating from those engines look for a way to attach a fixed score contribution to a sub-query without letting it affect matching. Naming the operator they already know makes labeled() discoverable from that starting point, instead of leaving them to infer the mapping from the Vespa-specific description of labels and itemRawScore.