[
https://issues.apache.org/jira/browse/SOLR-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681234#comment-13681234
]
Yonik Seeley commented on SOLR-4221:
------------------------------------
bq. In case of "implicit" router , we do not wish to assign shard names
Right - I was more talking about the default when we were already using the
compositeId router.
It seems like that for the collections API, defaulting to router=compositeId
and numShards=1 is reasonable.
bq. Is it possible to create collection w/ no shard?, or we do we need to add
support for that first?
I don't think the collections API currently has support for routers other than
the default compositeId (just tried it... I get a NPE if I don't provide
numShards). There may be issues at a lower level too - not sure (initially,
collections were created by bringing up a core - the collections API came
later).
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
