[GEODE-10294] Need to consider invalid token when comparing value during putIfAbsent

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.15.0, 1.16.0
• Fix Version/s: 1.15.0, 1.16.0
• Component/s: regions
• Labels: blocks-1.15.0 pull-request-available
• Assignee: Eric Shu
• Reporter: Eric Shu
• Created: 10/May/22 19:12
• Updated: 22/Jun/22 20:46
• Resolved: 01/Jun/22 20:40

Description

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.

Issue Links

• links to: GitHub Pull Request #7679
• links to: GitHub Pull Request #7704
• links to: GitHub Pull Request #7738