You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/05/13 23:22:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17536932#comment-17536932 ]
ASF subversion and git services commented on GEODE-10294:
---------------------------------------------------------
Commit 4f4af2a303142729708a951cc8a93f562c3de8bc in geode's branch refs/heads/develop from Eric Shu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4f4af2a303 ]
GEODE-10294: Compare invalid token during putIfAbsent retry. (#7679)
* During putIfAbsent retry, comparing invalid token value when
putIfAbsent of a null value instead.
> 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
> Reporter: Eric Shu
> Assignee: Eric Shu
> Priority: Major
> Labels: blocks-1.15.0, pull-request-available
>
> 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)