lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-5353) Enhance CoreAdmin api to split a route key's documents from an index
Date Fri, 18 Oct 2013 16:08:52 GMT

     [ 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-allow-single-range.patch

Allow CoreAdmin split to accept a single range only

> 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-allow-single-range.patch, 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message