[jira] [Updated] (SOLR-14477) relatedness() values can be wrong when using 'prefix'

["Chris M. Hostetter (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-14477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris M. Hostetter updated SOLR-14477:
--------------------------------------
    Attachment: SOLR-14477.patch
      Assignee: Chris M. Hostetter
        Status: Open  (was: Open)

patch with test case and fix to make test pass (but i'm not convinced there aren't still problematic code paths not covered by these test changes)

> relatedness() values can be wrong when using 'prefix'
> -----------------------------------------------------
>
>                 Key: SOLR-14477
>                 URL: https://issues.apache.org/jira/browse/SOLR-14477
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Chris M. Hostetter
>            Assignee: Chris M. Hostetter
>            Priority: Major
>         Attachments: SOLR-14477.patch
>
>
> Another {{relatedness()}} bug found in json facet's while working on increased test coverage for SOLR-13132.
> if the {{prefix}} option is used when doing a terms facet, then the {{relatedess()}} calculations can be wrong in some situations -- most notably when using {{limit:-1}} but i'm pretty sure the bug also impacts the code paths where the (first) {{sort}} (or {{prelim_sort}} is computed against the  {{relatedness()}} values.
> Real world impacts of this bug should be relatively low since i can't really think of any practical usecases for using  {{relatedness()}} in conjunction with {{prefix}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org