[ https://issues.apache.org/jira/browse/GEODE-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545132#comment-17545132 ]
ASF subversion and git services commented on GEODE-10294: --------------------------------------------------------- Commit 34e15feb97b0aa932dae6c41e5e8a01332522db1 in geode's branch refs/heads/support/1.15 from Eric Shu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=34e15feb97 ] GEODE-10294: Compare invalid token during putIfAbsent retry. (#7738) * During putIfAbsent retry, comparing invalid token value when putIfAbsent of a null value. * Do not make putIfAbsent event to update event if current entry value is null or invalidate and is a retried event. (cherry picked from commit ea48e7f7c0e8f272957377030ab28f7f87da8eac) > 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)