[
https://issues.apache.org/jira/browse/LUCENE-7833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016964#comment-16016964
]
ASF subversion and git services commented on LUCENE-7833:
---------------------------------------------------------
Commit 8a88eaf0dc33c4c6ac1f1b6fb499d971345dcb76 in lucene-solr's branch
refs/heads/branch_6_6 from [~jpountz]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8a88eaf ]
LUCENE-7833: Fix score computation with ToParentBlockJoinQuery and
ScoreMode.MAX.
> 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
> Attachments: LUCENE-7833.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
