[
https://issues.apache.org/jira/browse/SOLR-11129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107358#comment-16107358
]
Shawn Heisey commented on SOLR-11129:
-------------------------------------
I've been talking with this user on IRC. Here's a summary:
It seems that facet parameters in localparams only apply at the shard level,
rather than the whole collection. So if "f.workflow.assignedTo.facet.mincount"
is in the localparam, and there are enough docs with the field value in one
shard, then it shows up in the output, and depending on how the mincount
matches up with the count in each shard, the number of docs in the response
might not be correct for the whole collection. If
"f.workflow.assignedTo.facet.mincount" is a URL parameter instead of part of
locaparams, then it works completely as expected.
The burning question: Is this a bug, or an expected change due to new
capability or some other bugfix? It's definitely a regression for the user --
everything works for them in version 4.9, but doesn't in 6.6, 5.5.3, and 4.10.4.
> Distributed facet search with localparm facet.mincount doesn't work in a
> multi shard cloud env.
> -----------------------------------------------------------------------------------------------
>
> Key: SOLR-11129
> URL: https://issues.apache.org/jira/browse/SOLR-11129
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 4.10.4, 5.5.4, 6.6.1
> Reporter: Gregory Loscombe
>
> Steps:-
> - Create a solr cloud setup, with 2 shards
> - Add some data to facet search on
> - Add a query where you filterquery against a field
> - And then create a facet key with some localparams, including facet.mincount
> Results:-
> - If you set facet.mincount as a local param of the facet, it will be ignored
> and always return items with a count of 0
> Expected:-
> - Should apply the localparam facet.mincount correctly in distributed facet
> search
> Notes:-
> - This is a regression from 4.9 where it worked (we have encountered this
> breaking change whilst trying to upgrade our current cluster)
> - Included some dummy test data to illustrate and the query output
> - If you have the facet.mincount not as a local param it does apply
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
