-
Notifications
You must be signed in to change notification settings - Fork 11
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
boostedfields for query #1510
boostedfields for query #1510
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most of the stuff in BoostedFields
is redundant, see EsMappings
.
I suggest letting QueryParams
handle the parameters and move the boost computing stuff into QueryUtil
(where all that is needed should be available).
new version... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! The entity type (determining which boosting mode to apply) needs to be fetched in a different way. See separate comment.
Otherwise I think this should work...? Obviously needs some cleaning up too.
|
||
Map<String, String[]> queryParameters = new HashMap<>(ogQueryParameters); | ||
|
||
String[] originalTypeParam = queryParameters.get("@type"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This won't work in the new style API since we don't put properties as separate parameters. Instead we have to extract the type from the query tree that get from _q
(+applied filters).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thumbs up ;)
Completed in #1531 |
Tentative attempt at boosting fields.