[
https://issues.jboss.org/browse/ISPN-8400?page=com.atlassian.jira.plugin....
]
Ryan Emerson commented on ISPN-8400:
------------------------------------
[~epbernard] Good point. I think for a generic shared memory use-case where we don't
know what is more important for the users data that you're right and REMOVE_ALL is the
better choice as it will be more predictable and easier for the user to reason about.
Adjust merge policies for JDG Online Services
---------------------------------------------
Key: ISPN-8400
URL:
https://issues.jboss.org/browse/ISPN-8400
Project: Infinispan
Issue Type: Feature Request
Components: Cloud Integrations
Reporter: Sebastian Ćaskawiec
Assignee: Ryan Emerson
Both Shared Memory and Caching Service require custom merge policies.
In Caching Service we need to clear out all conflicted entries upon split brain. Shared
Memory service might be a little bit more tricky and we might want to use some different
strategy (but that needs to be checked out).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)