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 2019/01/09 01:14:00 UTC

[jira] [Commented] (GEODE-6260) Set iterator moveNext() in transaction should not cleanup non-dirty entries when encountering destroyed entry

    [ https://issues.apache.org/jira/browse/GEODE-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737713#comment-16737713 ] 

ASF subversion and git services commented on GEODE-6260:
--------------------------------------------------------

Commit 1128afb57bae226a0645c074fff621980122a689 in geode's branch refs/heads/feature/GEODE-6260 from eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1128afb ]

GEODE-6260: Do not cleanup non-dirty entries in transactional set operation


> Set iterator moveNext() in transaction should not cleanup non-dirty entries when encountering destroyed entry
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6260
>                 URL: https://issues.apache.org/jira/browse/GEODE-6260
>             Project: Geode
>          Issue Type: Bug
>          Components: transactions
>    Affects Versions: 1.9.0
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>
> Destroyed entry is not saved in the txState during set operation. However, there is a code path that non dirty entries are cleaned up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)