We are using collapsingQParser to group results for collapsing possible duplicate records.
We have a signature field that the collapsingQParser acts on to group the results. However, when we facet on top of it, we get facet counts that are seemingly wrong. For example, if we have 4 records: Signature availability 1 pub 1 conf 2 conf 2 conf When we run a search of *:*, we get 2 results back because there are two distinct signatures. When we facet on availability, we get pub -> 1 and conf ->1. But when we add the fq=availability:conf to the query (when user clicks on the facet), the count becomes 3. It's confusing for our users. After reading https://issues.apache.org/jira/browse/SOLR-6143, I understand why it behaves this way. collapsingQParser returns the facet count the same as group.truncate=true. I wanted to see if there are plans (in the near future) to add support for collapsingQParser where I could get untruncated count for facets. I don't want to use solr group because when group.ngroups=true, the performance is absolutely atrocious. Thanks, Rebecca Tang Applications Developer, UCSF CKM Legacy Tobacco Document Library<legacy.library.ucsf.edu/> E: rebecca.t...@ucsf.edu
