[
https://issues.apache.org/jira/browse/LUCENE-9991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17357646#comment-17357646
]
ASF subversion and git services commented on LUCENE-9991:
---------------------------------------------------------
Commit 4404b19142288e3780f1c0279205721545cf2917 in lucene's branch
refs/heads/main from Greg Miller
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=4404b19 ]
LUCENE-9991: Address bug in TestStringValueFacetCounts (#168)
> Fix TestStringValueFacetCounts
> ------------------------------
>
> Key: LUCENE-9991
> URL: https://issues.apache.org/jira/browse/LUCENE-9991
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/facet
> Affects Versions: main (9.0)
> Reporter: Greg Miller
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As
> [reported|https://issues.apache.org/jira/browse/LUCENE-9950?focusedCommentId=17357589&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17357589]
> by [~julietibs] in LUCNEE-9950, there's a randomized test failure in
> {{TestStringValueFacetCounts}}. It's actually an issue with the test itself.
> Since count ties are broken in {{StringValueFacetCounts}} by ordinal, but the
> test doesn't know anything about the ordinals, the test breaks ties by the
> value itself before comparing results. The edge-case is if we only request a
> topN of 1, but the top result ties in count with other results. In this
> scenario, the result returned by the {{Facets}} might be one that sorts
> higher than another when secondarily sorted by value, but the test can't
> solve for this since it only sees the one result. Should be a fairly simple
> fix in the test case itself. Will do so shortly.
--
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
