[
https://issues.apache.org/jira/browse/SOLR-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591412#comment-13591412
]
Shalin Shekhar Mangar commented on SOLR-3755:
---------------------------------------------
bq. How do we know what collection? I assume there will be a "collection"
parameter?
Yes, a collection param will also be present.
bq. 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!
Yes! That is exactly the thinking behind shard.keys here. It is not being
overloaded but used to indicate which shard to split by specifying the key
which resolves to a shard name.
bq. Related: SOLR-4503 - we now have the capability to use restlet, and should
consider doing so for new APIs like this.
I'm not familiar with restlet. I'll take a look at it.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
