[
https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17539645#comment-17539645
]
ASF subversion and git services commented on GEODE-10294:
---------------------------------------------------------
Commit 4be1a15f37afa678198984a578e15f4df3c26da9 in geode's branch
refs/heads/support/1.15 from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4be1a15f37 ]
Revert "GEODE-10294: Compare invalid token during putIfAbsent retry. (#7679)"
(#7704)
This reverts commit 4f4af2a303142729708a951cc8a93f562c3de8bc.
(cherry picked from commit b84d9c7f9423a1f2ec6b9932b32fd2e330a322ac)
> 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.15.0, 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)
