[
https://issues.apache.org/jira/browse/SOLR-14477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112510#comment-17112510
]
ASF subversion and git services commented on SOLR-14477:
--------------------------------------------------------
Commit 28209cb8b1fe2a4d8050e4877c4df2ad5d85509b in lucene-solr's branch
refs/heads/master from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=28209cb ]
SOLR-14492: Fix ArrayIndexOutOfBoundsException in json.facet 'terms' when
FacetFieldProcessorByHashDV is used with aggregations over multivalued numeric
fields
SOLR-14477: Fix incorrect 'relatedness()' calculations in json.facet 'terms'
when 'prefix' option is used
> 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, SOLR-14477.patch, 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
