[
https://issues.apache.org/jira/browse/SOLR-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681012#comment-13681012
]
Noble Paul commented on SOLR-4221:
----------------------------------
Assigning 'implicit' router in the absence of 'numShards' param is confusing
for the user. I would like it this way. there is a param caller 'router' whose
default is "compositeId" . if both 'numShards' and 'router' params are absent
the create action should fail stating 'numShards is a required param for
default 'compositeId' router.
Proposed modifications to the collection CREATE action
* creating a shard should be possible even if no nodes can be allocated to the
shard. As and when nodes come up , it can be allocated to the shard
* new required parameter 'shard' (multivalued) for 'implicit' route
New collection action , CREATE_SHARD
* params . 'shard' (multivalued) optional . It creates new shards and try to
allocate nodes for the same. If enough nodes are not available the shards will
remain in 'construction' state
* replicationFactor : (optional) if absent the value will be inherited from the
collection
New collection action , UPDATE_SHARD
* replicationFactor : provide a new value to add capacity to an existing shard
The name of the Router is a bit confusing. I fee it should be called "explicit"
instead of "implicit". But let us leave it
> Custom sharding
> ---------------
>
> Key: SOLR-4221
> URL: https://issues.apache.org/jira/browse/SOLR-4221
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
> Assignee: Noble Paul
>
> Features to let users control everything about sharding/routing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
