[
https://issues.apache.org/jira/browse/SOLR-14036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199521#comment-17199521
]
Munendra S N commented on SOLR-14036:
-------------------------------------
I had forgotten about this one. I have raised the PR(due to some reason it is
not linked in jira) - https://github.com/apache/lucene-solr/pull/1900
Removed the bunch of redundant checks from TermsComponent. Based on the
debugging, SOLR-3645 added distrib=false because shard requests also needs to
use /terms handler which wasn't possible in versions before 5x and needed
explicit shards.qt to be set to enabled distributed search. With SOLR-6311,
request path is used as qt for shard request if shards.qt and qt is not
specified which solves this issue
> 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
> 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
