[ https://issues.apache.org/jira/browse/GEODE-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723183#comment-16723183 ]
ASF subversion and git services commented on GEODE-5786: -------------------------------------------------------- Commit e8720ca6a28e2c6aa4769c85f14c4083c94504ba in geode's branch refs/heads/develop from pivotal-eshu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e8720ca ] GEODE-5786: Create txEntryState based on createIfAbsent condition. (#3008) * Do not create txEntryState for entries with tombstones during set operations - keySet, values, etc. * Only create txEntryState for tombstones during get operation. Co-authored-by: lgallinat > Iterating a region in a transaction puts destroyed keys in the tx state > ----------------------------------------------------------------------- > > Key: GEODE-5786 > URL: https://issues.apache.org/jira/browse/GEODE-5786 > Project: Geode > Issue Type: Bug > Reporter: Lynn Gallinat > Assignee: Lynn Gallinat > Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > In a region that has had an entry destroyed, the region will then contain a > tombstone for that key. > If a thread iterates the region in a transaction, then all keys in the region > are added to the transaction state. > The problem is that destroyed keys that have tombstones are also added to the > transaction set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)