-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
Rank_feature query should support sparse_vector field type #104090
Comments
Pinging @elastic/es-search (Team:Search) |
Pinging @elastic/ent-search-eng (Team:Enterprise Search) |
This is indeed interesting. I would hope we move sparse_vector further away from What do you think @jpountz ? |
@benwtrent Agreed, I'd rather preserve the ability to diverge these two fields in the future as they feel like they address different problems. That said, do we already have a query that allows computing the maximum inner product between a query vector and indexed vectors easily? Something like that may be a useful addition (and effectively be the same as a |
I don't think so. Right now the way to do it is a "bool[term1(boost1),...,termn(boostn)]". So, maybe we add a "sparse_vector" query? |
Closing this issue, as we decided to introduce a |
The rank_feature query boosts relevance scores based on numeric values of
rank_feature
orrank_features
fields.We should update this so it will also work with
sparse_vector
fields.The text was updated successfully, but these errors were encountered: