[
https://issues.apache.org/jira/browse/SOLR-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-5338:
----------------------------------------
Attachment: SOLR-5338.patch
Changes:
* Introduces two new methods in CompositeIdRouter
{code}
public List<Range> partitionRangeByKey(String key, Range range)
{code}
and
{code}
public Range routeKeyHashRange(String routeKey)
{code}
* The collection split action accepts a new parameter 'split.key'
* The parent slice is found and its range is partitioned according to split.key
* We re-use the logic introduced in SOLR-5300 to do the actual splitting.
> Split shards by a route key
> ---------------------------
>
> Key: SOLR-5338
> URL: https://issues.apache.org/jira/browse/SOLR-5338
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Fix For: 4.6, 5.0
>
> Attachments: SOLR-5338.patch
>
>
> Provide a way to split a shard using a route key such that all documents of
> the specified route key end up in a single dedicated sub-shard.
> Example:
> Assume that collection1, shard1 has hash range [0, 20]. Also that route key
> 'A!' has hash range [12,15]. Then invoking:
> {code}
> /admin/collections?action=SPLIT&collection=collection1&split.key=A!
> {code}
> should produce three sub-shards with hash range [0,11], [12,15] and [16,20].
> Specifying the source shard is not required here because the route key is
> enough to figure it out. Route keys spanning more than one shards will not be
> supported.
> Note that the sub-shard with the hash range of the route key may also contain
> documents for other route keys whose hashes collide.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
