[jira] [Commented] (GEODE-1044) Recovery from disk with an initial image put can lead to a duplicate entry in the index

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

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

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

Commit 54931a52ed3f2c3d72156f830edc637f00b7a8b1 in incubator-geode's branch refs/heads/develop from [~huynhja]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=54931a5 ]

GEODE-1044: InitialImagePut executes BEFORE_UPDATE_OP on indexes for updates

When entries are recovered from persistence, the values are added to the index,
however a gii can then occur where the initialImagePut needs to properly
alert the index that an update is occuring.  The BEFORE_UPDATE_OP allows the index
to retreive the oldKey and notifies the index that an update is occuring.

Refactor QueryTestUtils and removed unused code
Minor modification for QueryTestUtils to be more generic and not be specific to Portfolios


> Recovery from disk with an initial image put can lead to a duplicate entry in the index
> ---------------------------------------------------------------------------------------
>
>                 Key: GEODE-1044
>                 URL: https://issues.apache.org/jira/browse/GEODE-1044
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Jason Huynh
>            Assignee: Jason Huynh
>
> Test scenario:
> 2 nodes
> 1 Persistent region with entries
> 1 node is shut down while the other continues to do puts
> Bring back the shut down node via cache.xml
> The index will be created and populated with the disk entries, the following initial image adds another entry due to the update mechanism not notifying the index that a removal needs to happen first (due to the way the indexes had been changed to remove the reverse map by default, the indexes need a BEFORE_UPDATE_OP with a REMOVE to occur so that the old indexed key can be calculated)



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