You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2014/07/21 11:25:38 UTC
[jira] [Comment Edited] (SOLR-5958) Document (and fix) numShards
and router selection parameter in SolrCloud
[ https://issues.apache.org/jira/browse/SOLR-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068340#comment-14068340 ]
Noble Paul edited comment on SOLR-5958 at 7/21/14 9:25 AM:
-----------------------------------------------------------
bq.Though the bootstrap does not treat numShards as a required param, the Collection API does and throw an error if we don't specify numShards.
The collection API is not used to create the collection, but the STATE command does that. The STATE command would fail if numShards is not present, but the nodes will always send the value "1" if nothing else is configured
But the collection API has to use some numShards for a non 'implicit router' collection . Hence the router is implicit
Probably we need our documentation to improve
was (Author: noble.paul):
bq.Though the bootstrap does not treat numShards as a required param, the Collection API does and throw an error if we don't specify numShards.
The collection API is not used to create the collection, but the STATE command does that. The STATE command would fail if numShards is not present, but the nodes will always send the value "1" if nothing else is configured
> Document (and fix) numShards and router selection parameter in SolrCloud
> ------------------------------------------------------------------------
>
> Key: SOLR-5958
> URL: https://issues.apache.org/jira/browse/SOLR-5958
> Project: Solr
> Issue Type: Task
> Components: SolrCloud
> Reporter: Anshum Gupta
> Assignee: Anshum Gupta
> Priority: Minor
>
> Right now numShards works in rather mysterious ways (unless you know how it works). We should clearly document the following:
> * If we start SolrCloud with bootstrapping, without mentioning numShards parameter, it defaults to 1 and also defaults the router to 'implicit'.
> * Mentioning numShards param, defaults the router to compositeId.
> * Though the bootstrap does not treat numShards as a required param, the Collection API does and throw an error if we don't specify numShards.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org