You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Eric Shu (Jira)" <ji...@apache.org> on 2022/06/01 18:54:00 UTC

[jira] [Updated] (GEODE-10294) Need to consider invalid token when comparing value during putIfAbsent

     [ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Shu updated GEODE-10294:
-----------------------------
    Fix Version/s: 1.16.0

> Need to consider invalid token when comparing value during putIfAbsent
> ----------------------------------------------------------------------
>
>                 Key: GEODE-10294
>                 URL: https://issues.apache.org/jira/browse/GEODE-10294
>             Project: Geode
>          Issue Type: Bug
>          Components: regions
>    Affects Versions: 1.15.0, 1.16.0
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>              Labels: blocks-1.15.0, pull-request-available
>             Fix For: 1.16.0
>
>
> During retry of putIfAbsent, there is a possibility that value has been created by the initial operation. Geode treats this as a successful operation, so that client initiated the operation will also create the entry in its local cache. However, putIfAbsent of null is a special case, as an Invalid Token is created instead of null value being put into the region entry. Need to handle this special case for above value comparison.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)