[ 
https://issues.apache.org/jira/browse/SOLR-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16051798#comment-16051798
 ] 

Alessandro Benedetti commented on SOLR-6174:
--------------------------------------------

Hi [~hossman],
I think that a combination of SOLR-6780 and this issue is causing me this very 
annoying behavior in a 4.10.2 Solr Cloud cluster :

*Scenario*
I append a facet query in a request handler in the solrconfig.xml of a 
collection.

*Bug*
When I run a query, the facet query count is incorrect and specifically it is 
num_shards*correct_count .
So it seems an aggregation of duplicated facet queries.

Weird thing is that this affect all the facet queries, even the ones you send 
at runtime as request params.

The bug seems solved in Solr 6.5.x , so I guess we should be OK.

Cheers

> Facet count incorrect when duplicate facet queries (facet.query) are specified
> ------------------------------------------------------------------------------
>
>                 Key: SOLR-6174
>                 URL: https://issues.apache.org/jira/browse/SOLR-6174
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.7.2
>            Reporter: Scott Smerchek
>            Priority: Minor
>              Labels: facet
>
> A request like:
> {{facet=true&facet.query=test}} correctly returns
> {noformat}
> {
>   "facet_counts": {
>      "facet_queries": {
>         "test": 3
>      }
>   }
> } 
> {noformat}
> But, specifying the {{facet.query}} more than once like 
> {{facet=true&facet.query=test&facet.query=test}} will sum the results of both 
> queries, returning double the correct count.
> {noformat}
> {
>   "facet_counts": {
>      "facet_queries": {
>         "test": 6
>      }
>   }
> } 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to