[
https://issues.apache.org/jira/browse/SOLR-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587943#comment-13587943
]
Tim Vaillancourt commented on SOLR-4420:
----------------------------------------
I'll try out the patch to understand the implementation aspect more, but I
believe this would work for me granted it is atomic across the collection, as
I'm guessing it would be. This would solve what I am looking for and a bit more
as I am proposing something like SWAP/RENAME, which would provide only a 1-to-1
mapping.
> Please add support for atomic swapping for Collections in SolrCloud
> -------------------------------------------------------------------
>
> Key: SOLR-4420
> URL: https://issues.apache.org/jira/browse/SOLR-4420
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Affects Versions: 4.1
> Reporter: Tim Vaillancourt
> Fix For: 4.2, 5.0
>
>
> Similar to the concept of swapping regular Solr cores online, I'd like to
> request support for atomic swapping of entire Collections in SolrCloud.
> This would aid in online schema changes, online sharding changes, etc.
> Ideally the new collection would be in sync with the current when swapped.
> At a high level, I believe this could be achieved if replicas of CollectionA
> could be brought up in CollectionB, then swapped atomically when in sync. I
> imagine a momentary pause to updates would need to occur, which would be
> acceptable for at least my use cases.
> Currently I can create a new collection under a new collection name and swap
> paths in the application or rename the core, but this is not elegant/ideal.
> Thanks for everyone's hard work on Solr! Great software.
> Tim Vaillancourt
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
