Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.incubator.apache.org
Date: Thu, 4 Aug 2016 17:04:20 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: issues@geode.incubator.apache.org
Message-ID: <JIRA.12994092.1470088805000.226446.1470330260622@Atlassian.JIRA>
In-Reply-To: <JIRA.12994092.1470088805000@Atlassian.JIRA>
References: <JIRA.12994092.1470088805000@Atlassian.JIRA> <JIRA.12994092.1470088805904@arcas>
Subject: [jira] [Commented] (GEODE-1718) Region replace can return false
 when it should not and can fail with an NPE
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 04 Aug 2016 17:04:29 -0000


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

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

Commit 91e234f85a6f8dfe1eedd59f6978e3667d0fd92a in incubator-geode's branch refs/heads/develop from [~dschneider]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=91e234f ]

GEODE-1718: fix replace on overflowed entry

When replace checks the current value for equality
with the expected value it now gets it from
the EntryEventImpl which the replace operation
had already called setOldValue on.
Added a unit test that confirms that replace
works on an overflowed entry and also handles
INVALID values correctly.


> Region replace can return false when it should not and can fail with an NPE
> ---------------------------------------------------------------------------
>
>                 Key: GEODE-1718
>                 URL: https://issues.apache.org/jira/browse/GEODE-1718
>             Project: Geode
>          Issue Type: Bug
>          Components: regions
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>
> The Region replace method may return false when it should have returned true. The can happen on a region configured with overflow when the entry being replaced has overflowed to disk. It can also happen on a persistent region if the entry being replaced has not yet initialized its value from disk.
> The NPE happens under the same configurations but when the expected old value was serialized with PDX and read-serialized was set to true.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)