[infinispan-issues] [JBoss JIRA] (ISPN-8204) Remove should be conditional

[Pedro Ruivo (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13450954#comment-13450954 ] 

Pedro Ruivo commented on ISPN-8204:
-----------------------------------

1. ok
2. doesn't the conditional commands force to fetch the remote value (in the new primary owner) when topology changes? non-conditional commands with IGNORE_RETURN_VALUES doesn't need to do so. 
3. sometimes I wonder why do we still have flags... there are more cases where the flags are ignored than respected :) Anyway, I think the SKIP_CACHE_LOAD is ignored for conditional commands anyway. 

> Remove should be conditional
> ----------------------------
>
>                 Key: ISPN-8204
>                 URL: https://issues.jboss.org/browse/ISPN-8204
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 9.1.0.Final
>            Reporter: Radim Vansa
>            Assignee: Radim Vansa
>
> If {{cache.remove(k)}} is called on non-existent key, it should become a no-op, marking the command as unsuccessful, not writing the cache store and not replicating the change to backup owners. That makes the command effectively conditional (as it checks previous value), in the same way as {{cache.replace(k, newValue)}} is.
> While I think that this is the correct behaviour, it's a breaking change for transactions. Some transactions may become read-only and there are multiple tests in the testsuite that would be broken by this.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)