SQL: score is not calculated for a match statement when combined with filter-like statements
#29685
Labels
Comments
costin
added a commit
that referenced
this issue
May 21, 2018
Make all bool constructs use match/should (that is a query context) as that is controlled and changed to a filter context by ES automatically based on the sort order (_doc, field vs _sort) and trackScores. Fix #29685
costin
added a commit
that referenced
this issue
May 21, 2018
Make all bool constructs use match/should (that is a query context) as that is controlled and changed to a filter context by ES automatically based on the sort order (_doc, field vs _sort) and trackScores. Fix #29685
costin
added a commit
to costin/elasticsearch
that referenced
this issue
Jun 13, 2018
Make all bool constructs use match/should (that is a query context) as that is controlled and changed to a filter context by ES automatically based on the sort order (_doc, field vs _sort) and trackScores. Fix elastic#29685
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Original comment by @astefan:
A query like
SELECT SCORE(), * FROM library WHERE match(author,'dan')does calculate and output the score of the results, while something likeSELECT SCORE(), * FROM library WHERE match(author,'dan') AND (page_count IS NULL OR page_count > 200)doesn't.The reason seems to be the query in the first case it's simply creating a
matchwhile the second one is wrongly wrapping the samematchquery in aboolsfilter(which is not calculating the score by default). While ok to wrap it in abool, but maybe not inside afilter. I think the same outcome can be obtained by usingmuststatements instead offilterones only when the scoring is needed (the presence ofSCORE()anywhere in the query)?The text was updated successfully, but these errors were encountered: