[
https://issues.apache.org/jira/browse/SOLR-15114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281486#comment-17281486
]
Naoto Minami commented on SOLR-15114:
-------------------------------------
Thanks [~tflobbe] and [~dsmiley].
I think it's difficult to test completely including optimizations, such
Block-max WAND. One way I thought is prepare documents for BMW and predict
results manually then assert. However this way has high costs for
implementation and maintenance...
{quote}This reminds me of the longstanding issue of a lack of regular published
Solr benchmarks :(SOLR-10317
{quote}
Absolutely agree.
> 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: 10m
> 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: [email protected]
For additional commands, e-mail: [email protected]