[ https://issues.apache.org/jira/browse/LUCENE-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015757#comment-16015757 ]
selckin commented on LUCENE-7833: --------------------------------- Original poster found it and talked about it on irc with a few of us, i just wanted to highlight it would be an easy fix so it doesn't get lost I believe he said he was interested in creating a test for it > Calculating minimum score instead of maximum score in > ToParentBlockJoinQuery.BlockJoinScorer.setScoreAndFreq > ------------------------------------------------------------------------------------------------------------ > > Key: LUCENE-7833 > URL: https://issues.apache.org/jira/browse/LUCENE-7833 > Project: Lucene - Core > Issue Type: Bug > Reporter: Bernhard Altendorfer > > We recently upgraded our Elasticsearch cluster from 5.3 to 5.4 and found a > bug when we score nested documents. > I spent some time to check the code from Elasticsearch and Lucene and I found > a problem in ToParentBlockJoinQuery.BlockJoinScorer.setScoreAndFreq. > In the switch statement for the scoreMode in the case "Max" the function > Math.min is used and I guess it should be Math.max. > This would explain our problem in Elasticsearch because we see exactly the > problem that instead of the maximum the minimum is returned. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org