[
https://issues.apache.org/jira/browse/LUCENE-9952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Miller resolved LUCENE-9952.
---------------------------------
Fix Version/s: 9.1
Resolution: Fixed
> FacetResult#value can be inaccurate in SortedSetDocValueFacetCounts
> -------------------------------------------------------------------
>
> Key: LUCENE-9952
> URL: https://issues.apache.org/jira/browse/LUCENE-9952
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/facet
> Affects Versions: 9.0
> Reporter: Greg Miller
> Assignee: Greg Miller
> Priority: Minor
> Fix For: 9.1
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> As described in a dev@ list
> [thread|http://mail-archives.apache.org/mod_mbox/lucene-dev/202105.mbox/%3CCANJ0CDo-9zt0U_pxWNOBkfiJpaAXZGGwOEJPnENAP6JzWz_t9Q%40mail.gmail.com%3E],
> the value of {{FacetResult#value}} can be incorrect in SSDV faceting when
> docs are multi-valued (affects both {{SortedSetDocValueFacetCounts}} and
> {{ConcurrentSortedSetDocValueFacetCounts}}). If a doc has multiple values in
> the same dimension, it will be counted multiple times when populating the
> counts of {{FacetResult#value}}.
> We should either provide an accurate count, or provide {{-1}} if we don't
> have an accurate count (like we do in taxonomy faceting). I _think_ this
> change will be a bit involved though as SSDV facet counting likely needs to
> be made aware of {{FacetConfig}}.
> NOTE: I've updated this description to describe only the SSDV case after
> spinning off LUCENE-9953 to track the LongValueFacetCounts case.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
