[ 
https://issues.apache.org/jira/browse/SOLR-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shalin Shekhar Mangar updated SOLR-5353:
----------------------------------------

    Attachment: SOLR-5353.patch

Changes:
# CoreAdmin SPLIT accepts a split.key parameter
# SolrIndexSplitter matches the split.key to the route key read from the id 
field
# Added a test which uses two split keys that have the same hash in murmur2

The way we extract the route key from the id field is a hack -- this 
functionality should ideally be inside CompositeIdRouter. I'll open an issue.

> Enhance CoreAdmin api to split a route key's documents from an index
> --------------------------------------------------------------------
>
>                 Key: SOLR-5353
>                 URL: https://issues.apache.org/jira/browse/SOLR-5353
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Shalin Shekhar Mangar
>            Assignee: Shalin Shekhar Mangar
>            Priority: Minor
>             Fix For: 4.6, 5.0
>
>         Attachments: SOLR-5353.patch
>
>
> Allow a split key to be passed in to CoreAdmin SPLIT action so that we can 
> split only a particular route key's documents out of the index.
> e.g. consider an index containing documents belonging to two route keys with 
> hash ranges A!=[12,15] and B!=[13,17]. We want to split all documents having 
> route key 'A!' while leaving behind any documents having route key 'B!' even 
> though some documents with 'B!' fall into the hash range of 'A!'
> This is different from what was achieved in SOLR-5338 because that issue 
> splits all documents belonging to the hash range of a given route key. Since 
> multiple keys can have overlapping hash range and we were splitting into the 
> same collection, we had no choice but to move all documents belonging to the 
> hash range into the new shard.
> In this particular issue, we are trying to migrate documents to a different 
> collection and therefore we can leave documents having other route keys 
> behind.



--
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

Reply via email to