[
https://issues.apache.org/jira/browse/SOLR-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787977#comment-13787977
]
Shalin Shekhar Mangar edited comment on SOLR-5308 at 10/7/13 2:59 PM:
----------------------------------------------------------------------
I think the way it can be made to work is by using the routing key (shard.key
or as it is known now _route_) to split an index. The target collection must be
specified as a request parameter. The target shard can be looked up
automatically using the hash of the routing key against the shards of target
collection. Optionally, requests for that shard.key can be automatically
forwarded to the target collection for a limited amount of time once the split
is complete.
was (Author: shalinmangar):
I think the way it can be made to work is by using the routing key (shard.key
or as it is known now _route_) to split an index. The target collection can be
specified as a request parameter. The target shard can be looked up
automatically using the hash of the shard.key against the shards of target
collection. Optionally, requests for that shard.key can be automatically
forwarded to the target collection for a limited amount of time once the split
is complete.
> Split a shard into a shard in another collection
> ------------------------------------------------
>
> Key: SOLR-5308
> URL: https://issues.apache.org/jira/browse/SOLR-5308
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: 5.0, 4.6
>
>
> Enable SolrCloud users to split out a set of documents from a single shard
> into a shard in another collection.
> This will be useful in multi-tenant environments. This feature will make it
> possible to split a tenant out of a shard and put it into its own collection
> which can be scaled separately.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
