[SOLR-7452] json facet api returning inconsistent counts in cloud set up

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.1
• Fix Version/s: 7.0
• Component/s: Facet Module
• Labels: count facet sort
• Assignee: Yonik Seeley
• Reporter: Vamsi Krishna D
• Created: 23/Apr/15 10:05
• Updated: 29/Aug/17 23:48
• Resolved: 15/Jun/17 16:55

Description

While using the newly added feature of json term facet api (http://yonik.com/json-facet-api/#TermsFacet) I am encountering inconsistent returns of counts of faceted value ( Note I am running on a cloud mode of solr). For example consider that i have txns_id(unique field or key), consumer_number and amount. Now for a 10 million such records , lets say i query for

q=:&rows=0&
json.facet={
biskatoo:{
type : terms,
field : consumer_number,
limit : 20,
sort :

{y:desc}

,
numBuckets : true,
facet:

{ y : "sum(amount)" }

}
}

the results are as follows ( some are omitted ):

"facets":{
"count":6641277,
"biskatoo":{
"numBuckets":3112708,
"buckets":[

{ "val":"surya", "count":4, "y":2.264506}

,

{ "val":"raghu", "COUNT":3, // capitalised for recognition "y":1.8}

,

{ "val":"malli", "count":4, "y":1.78}

]}}}

but if i restrict the query to

q=consumer_number:raghu&rows=0&
json.facet={
biskatoo:{
type : terms,
field : consumer_number,
limit : 20,
sort :

{y:desc}

,
numBuckets : true,
facet:

{ y : "sum(amount)" }

}
}

i get :

"facets":{
"count":4,
"biskatoo":{
"numBuckets":1,
"buckets":[

{ "val":"raghu", "COUNT":4, "y":2429708.24}

]}}}

One can see the count results are inconsistent ( and I found many occasions of inconsistencies).

I have tried the patch https://issues.apache.org/jira/browse/SOLR-7412 but still the issue seems not resolved

Issue Links

• is duplicated by: SOLR-11138 JSON terms facet counts change when changing limit parameter
• is related to: SOLR-8768 Wrong behaviour in json facets
• relates to: SOLR-11159 Facet buckets count missing after passing {refine:true} | SOLR-7542

Sub-Tasks

• JSON Facet refactoring to support refinement: Resolved