[SOLR-12556] JSON Field Facet refinement can return incorrect counts/stats for sorted buckets -- when using processEmpty

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Facet Module
• Assignee: Unassigned
• Reporter: Chris M. Hostetter
• Created: 16/Jul/18 18:43
• Updated: 07/Jan/22 17:38

Description

Creating this spin off of SOLR-12343 - the fix in that issue addresses the most common cases, but does not help when processEmpty:true is used...

in getRefinement() you've got returnedAllBuckets taking into consideration processEmpty:true - so that even if a shardA doesn't say it has more:true we will still send it candidate bucketX for refinement if we didn't explicitly saw bucketX on shardA. so far so good.

but then, once all the refinement is done, and we have a fully refined bucketX it might now sort "lower" then an incomplete bucketY ... and isBucketComplete doesn't pay any attention to processEmpty:true ... so it sees that shardA does not have more:true and thinks (the incomplete) bucketY is ok to return.

Issue Links

• is fixed by: SOLR-15836 Address counterintuitive behavior of JSON "terms" subfacet refinement
• relates to: SOLR-12343 JSON Field Facet refinement can return incorrect counts/stats for sorted buckets