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

ASF subversion and git services commented on SOLR-14036:
--------------------------------------------------------

Commit ac5847231017f12d6a51348e1cdbd50c9732a224 in lucene-solr's branch 
refs/heads/master from Munendra S N
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=ac58472 ]

SOLR-14036: Remove explicit distrib=false from /terms handler (#1900)

* Remove distrib=false from /terms handler so that terms are returned from 
across all shards instead of a single local shard.
* cleanup shards parameter handling in TermsComponent. This is handled in 
HttpShardHandler
* Remove redundant tests for shard whitelist
* remove redundant terms params from ScoreNodeStream


> 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
>            Assignee: Munendra S N
>            Priority: Major
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to