[
https://issues.apache.org/jira/browse/SOLR-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742581#action_12742581
]
Hoss Man commented on SOLR-1331:
--------------------------------
bq. I was thinking about more safe-guards like acquiring locks on source cores
to make sure a writer is not opened on them until the merge completes.
Ah... gotcha. yeah, it makes sense that the existing merge API (that requires
you to have an index path) can get away with not worrying about this (making it
the callers responsibility) but a more user-freindly api for merging by core
name should probably hide this from the user.
another option might just be to require that the (src) core is UNLOADed first.
> Support merging multiple cores
> ------------------------------
>
> Key: SOLR-1331
> URL: https://issues.apache.org/jira/browse/SOLR-1331
> Project: Solr
> Issue Type: New Feature
> Components: update
> Reporter: Shalin Shekhar Mangar
> Fix For: 1.5
>
>
> There should be a provision to merge one core with another. It should be
> possible to create a core, add documents to it and then just merge it into
> the main core which is serving requests. This way, the user will not need to
> know the filesystem as it is needed for SOLR-1051
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
