[jira] [Commented] (GEODE-3996) CacheWriter methods that call EntryEvent.getOldValue may see it return null even when a non-null old value exists

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

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

Commit 9221905bbf3343e18d5514e14c3dc7f9ba5d0eae in geode's branch refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9221905b ]

Feature/GEODE 3996 (#1073)

GEODE-3996: change CacheWriter getOldValue to return value

If the old value is overflowed to disk and a CacheWriter calls getOldValue
it will now return the value overflowed to disk instead of null (the old behavior).

Serialization of EntryEventImpl now correctly handles old value that is NOT_AVAILABLE.


> CacheWriter methods that call EntryEvent.getOldValue may see it return null even when a non-null old value exists
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-3996
>                 URL: https://issues.apache.org/jira/browse/GEODE-3996
>             Project: Geode
>          Issue Type: Bug
>          Components: regions
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>
> If a region configures eviction with overflow to disk then it is possible that a CacheWriter method that calls EntryEvent.getOldValue may see it return null. This happens when the old value for that entry was evicted to disk.
> In the case of a CacheWriter, geode should in this case ask for the old value that is on disk and return it.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)