[
https://issues.apache.org/jira/browse/SOLR-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050139#comment-13050139
]
Hoss Man commented on SOLR-2593:
--------------------------------
one thing to think about when talking about the API is how the implementation
will actually work.
the fq type option is basically going to require making a full copy of hte
index and then deleting by query. (unless i'm missing something) but for people
who don't care how the index is partitioned a more efficient approach could
probably happen by working at the segment level -- let the user say "split off
a hunk of at least 20% but no more then 50%" and then you can look at
individual segments and doc counts and see if it's possible to just move
segments around (and maybe only do the "copy+deleteByQuery" logic on a single
segment.
> A new core admin command 'split' for splitting index
> ----------------------------------------------------
>
> Key: SOLR-2593
> URL: https://issues.apache.org/jira/browse/SOLR-2593
> Project: Solr
> Issue Type: New Feature
> Reporter: Noble Paul
> Fix For: 4.0
>
>
> If an index is too large/hot it would be desirable to split it out to another
> core .
> This core may eventually be replicated out to another host.
> There can be to be multiple strategies
> * random split of x or x%
> * fq="user:johndoe"
> example
> example :
> command=split&split=20percent&newcore=my_new_index
> or
> command=split&fq=user:johndoe&newcore=john_doe_index
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
