[ 
https://issues.apache.org/jira/browse/SOLR-15114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281428#comment-17281428
 ] 

Tomas Eduardo Fernandez Lobbe commented on SOLR-15114:
------------------------------------------------------

bq. Can we have a test for the optimization itself somehow? 
I remember looking when this was implemented and I couldn't find a way to 
really assert if the optimization was being applied, I'll take another look, 
but let me know if you have any idea. Maybe [~jpountz]? In this particular 
case, even the {{ImpactDISI}} would have been used, except that the skipping 
would have been very sub-optimal. 
bq. was this bug here from the beginning when Solr added support for the 
optimization, or it it unique to 8.6.3, or some release inbetween?
This has been like this since 8.6.0: SOLR-14554

> 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: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to