[
https://issues.apache.org/jira/browse/KARAF-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ioannis Canellos resolved KARAF-1081.
-------------------------------------
Resolution: Fixed
Committed to trunk and merge into 2.2.x
> Cellar should provide a Hazelcast merge policy.
> -----------------------------------------------
>
> Key: KARAF-1081
> URL: https://issues.apache.org/jira/browse/KARAF-1081
> Project: Karaf
> Issue Type: New Feature
> Affects Versions: cellar-2.2.2, cellar-2.2.1
> Reporter: Ioannis Canellos
> Assignee: Ioannis Canellos
> Fix For: cellar-3.0.0, cellar-2.2.3
>
>
> In Hazelcast it is possible to have a network split and network merge.
> After the merge hazelcast attempts to merge the data from the 2 clusters.
> In Cellar we often use maps that contain lists, or sets as a value.
> Usaly those sets contain a list of nodes (e.g. group of members or dosgi
> service providers etc).
> We should provide a merge policy that will make sure those maps (containing
> sets) will be properly merged back together.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
