[
https://issues.apache.org/jira/browse/SOLR-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-4420.
-------------------------------
Resolution: Duplicate
> 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.6
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
