-
Notifications
You must be signed in to change notification settings - Fork 24.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it easier to boost by field value #49761
Labels
>enhancement
:Search Relevance/Ranking
Scoring, rescoring, rank evaluation.
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
Comments
Pinging @elastic/es-search (:Search/Ranking) |
Pinging @elastic/es-search (Team:Search) |
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>enhancement
:Search Relevance/Ranking
Scoring, rescoring, rank evaluation.
Team:Search Relevance
Meta label for the Search Relevance team in Elasticsearch
I have seen a couple users wanting to boost documents based on the category that documents belong to end up with a query that looked like this:
These queries have tens or hundreds of functions, for each category that they are trying to boost differently, and that need to be evaluated in order until one of them matches (which typically still requires to evaluate half the filters on average since values are usually exclusive). It is possible to do something that usually performs better with a script:
But it is still far from being ideal. For instance scripts have to do the ordinal->value lookup here while what we'd really want would be to make this work on top of ordinals. This seems to be a common problem to me, can we add a new query that would help solve this problem?
The text was updated successfully, but these errors were encountered: