[
https://issues.apache.org/jira/browse/SOLR-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588809#comment-13588809
]
Yonik Seeley commented on SOLR-3755:
------------------------------------
{quote}
"The collections api may be invoked as follows:
http://host:port/solr/admin/collections?action=SPLIT&shard=<shard_1>&shard=<shard_2>
{quote}
Ok, I assume this is for splitting more than one shard (i.e. both shard_1 and
shard_2 in this example will be split?)
How do we know what collection? I assume there will be a "collection"
parameter?
Related: SOLR-4503 - we now have the capability to use restlet, and should
consider doing so for new APIs like this.
{quote}
Sometimes, shard names are automatically assigned by SolrCloud and it may be
more convenient for users to specify shards by shard keys instead of shard
names e.g.
http://host:port/solr/admin/collections?action=SPLIT&shard.keys=shardKey1,shardKey2"
{quote}
shard.keys is currently used in routing request (and the values are often not
shard names), so we probably shouldn't overload it here. After all, it may
make sense in the future to be able to use shard.keys to specify which shard
you want to split!
> shard splitting
> ---------------
>
> Key: SOLR-3755
> URL: https://issues.apache.org/jira/browse/SOLR-3755
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Yonik Seeley
> Attachments: SOLR-3755-CoreAdmin.patch, SOLR-3755.patch,
> SOLR-3755.patch, SOLR-3755-testSplitter.patch, SOLR-3755-testSplitter.patch
>
>
> We can currently easily add replicas to handle increases in query volume, but
> we should also add a way to add additional shards dynamically by splitting
> existing shards.
--
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]