[
https://issues.apache.org/jira/browse/SOLR-15114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283204#comment-17283204
]
ASF subversion and git services commented on SOLR-15114:
--------------------------------------------------------
Commit b6db6c88d7bc4ee1757c450ad7a3df8b72add084 in lucene-solr's branch
refs/heads/master from Tomas Eduardo Fernandez Lobbe
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=b6db6c8 ]
SOLR-15114: Add CHANGES entry
> WAND does not work correctly on multiple segments in Solr 8.6.3
> ---------------------------------------------------------------
>
> Key: SOLR-15114
> URL: https://issues.apache.org/jira/browse/SOLR-15114
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.6.3, master (9.0)
> Reporter: Naoto Minami
> Assignee: Tomas Eduardo Fernandez Lobbe
> Priority: Blocker
> Fix For: master (9.0), 8.8.1
>
> Attachments: wand.pdf
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Solr 8.6.3, minCompetitiveScore of WANDScorer resets to zero for each
> index segment and remain zero until maxScore is updated.
> There are two causes of this problem:
> - MaxScoreCollector does not set minCompetitiveScore of
> MinCompetitiveScoreAwareScorable newly generated for another index segment.
> - MaxScoreCollector updates minCompetitiveScore only if maxScore is updated.
> This behavior is correct considering the purpose of MaxScoreCollector.
> For details, see the attached pdf.
> *Note*
> This problem occurs in distributed search (SolrCloud) or the fl=score
> parameter specified.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
