[
https://issues.apache.org/jira/browse/SOLR-14036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992358#comment-16992358
]
Munendra S N commented on SOLR-14036:
-------------------------------------
[~antogruz]
Thanks for sharing the request. As shared above, {{/terms}} by default doesn't
do distributed queries (because of setting) that's why the difference in
response based on which shard the request is being sent to.
I'm not aware of the reason for disabling distributed queries by default for
{{/terms}}, we might need to check git history. For now, you could either pass
{{distrib=true}} or pass {{shards}} parameter which would enable distributed
queries and unblock you.
Once we know the reason for {{distrib=false}} setting, then we could decide if
that needs to be changed or not.
> TermsComponent distributed search (shards) doesn't work with SolrCloud
> ----------------------------------------------------------------------
>
> Key: SOLR-14036
> URL: https://issues.apache.org/jira/browse/SOLR-14036
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SearchComponents - other
> Reporter: David Smiley
> Priority: Major
>
> My colleagues [~bruno.roustant] and [~antogruz] attempted to use the
> {{TermsComponent}} in SolrCloud on a collection with multiple shards. The
> results were inconsistent depending on which shard the client was talking
> with. Looking at the prepare() method, I can see this component reads the
> "shards" param. It should not have been coded that way; the SearchHandler or
> related machinery is responsible for parsing/processing that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
