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
Upgrade to lucene-5.2-snapshot-1675363. #10727
Upgrade to lucene-5.2-snapshot-1675363. #10727
Conversation
Explanation boostExpl = Explanation.match(maxBoost, "maxBoost"); | ||
Explanation minExpl = Explanation.match( | ||
Math.min(funcExpl.getValue(), maxBoost), | ||
"Math.min of", |
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.
should we just say min of or minimum of?
Looks great. I think in general i prefer "min of" or "minimum of" where we currently say "Math.min of", because that only makes sense to java developers. Otherwise I am happy the equals/hashcode are all using superclass methods, and ComplexExplanation is out of here. |
Thanks Robert. I kept the explanation descriptions as they were but I don't mind applying the fixes you suggest. We might find more bugs in equals/hashcode as we migrate to queries which recursively call QueryUtils.check on sub queries on the contrary to filters. |
Indeed, they were in the CombineFunction before that way (I missed that). I thought they were newly introduced here. |
This snapshot contains in particular LUCENE-6446 (refactored explanation API) and LUCENE-6448 (better equals/hashcode for filters).
5142b60
to
dd679a3
Compare
…75363 Upgrade to lucene-5.2-snapshot-1675363.
This is backported from elastic#10727. closes elastic#10742
This snapshot contains in particular LUCENE-6446 (refactored explanation API)
and LUCENE-6448 (better equals/hashcode for filters).
Closes #10728