[ https://issues.apache.org/jira/browse/LUCENE-7132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15313941#comment-15313941 ]
Michael McCandless commented on LUCENE-7132: -------------------------------------------- A bit more progress ... it looks like somehow {{BooleanScorer}} gets confused and is collecting a window with more than one sub-scorer matching, yet failed to tell the top collector to reset back to the fake scorer (it's still on a boosted scorer, I think from a prior window that had only one matching sub, incorrectly applying a 0.3333 boost). > BooleanQuery scores can be diff for same docs+sim when using coord (disagree > with Explanation which doesn't change) > ------------------------------------------------------------------------------------------------------------------- > > Key: LUCENE-7132 > URL: https://issues.apache.org/jira/browse/LUCENE-7132 > Project: Lucene - Core > Issue Type: Bug > Components: core/search > Affects Versions: 5.5 > Reporter: Ahmet Arslan > Assignee: Steve Rowe > Attachments: LUCENE-7132.patch, LUCENE-7132.patch, LUCENE-7132.patch, > SOLR-8884.patch, SOLR-8884.patch, debug.xml > > > Some of the folks > [reported|http://find.searchhub.org/document/80666f5c3b86ddda] that sometimes > explain's score can be different than the score requested by fields > parameter. Interestingly, Explain's scores would create a different ranking > than the original result list. This is something users experience, but it > cannot be re-produced deterministically. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org