[jira] [Commented] (GEODE-4823) Indexes should not be updated on a destroy if the old value is a TOMBSTONE

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

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

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

Commit 140118d066dc5da914d23eb79313148c3462721e in geode's branch refs/heads/develop from [~nabarunnag]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=140118d ]

GEODE-4823: OQL index not updated for tombstone (#1603)

* If the region entry is a tombstone then OQL indexes are not updated
	* The operation extracted to a external method.

> Indexes should not be updated on a destroy if the old value is a TOMBSTONE
> --------------------------------------------------------------------------
>
>                 Key: GEODE-4823
>                 URL: https://issues.apache.org/jira/browse/GEODE-4823
>             Project: Geode
>          Issue Type: Bug
>          Components: querying
>            Reporter: Jason Huynh
>            Assignee: Jason Huynh
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> If a destroy operation is called but the old value is a TOMBSTONE, the index operation is a no op but certain indexes may spend cycles trying to locate the entry in the index.
>  
> Instead we should short circuit and ignore an operation if the action is DESTROY and the old value is a TOMBSTONE



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