[
https://issues.apache.org/jira/browse/SOLR-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16054839#comment-16054839
]
Anshum Gupta commented on SOLR-5958:
------------------------------------
Coming back to this after a really long time. It's a low hanging one, and would
make things easier for the end user to understand if we standardize it.
Should we default numShards to 1 and keep things simple? We should segregate
the router selection, and numShards and have simple defaults for both.
Default numShards = 1, and router = compositeId (so the user can come back
later and split shard, etc.).
> 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: documentation, 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
