[
https://issues.apache.org/jira/browse/SOLR-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742328#action_12742328
]
Shalin Shekhar Mangar commented on SOLR-1331:
---------------------------------------------
bq. Is the thinking here that we just expose SOLR-1051 type functionality at
the core level w/o using file paths - in which case the caller is responsible
for knowing whether or not the index merging makes logical sense
Yes, that is the motivation. However, 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.
bq. are we talking about a more user friendly concept of core merging where we
sanity check that the schemas are the same - or even more complex: merge the
schemas if they don't have any conflicts (ie: all field/type names in common
have identical declarations?)
That'd be cool but also more complex. We can do that if users ask for it.
> 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.
