[
https://issues.apache.org/jira/browse/GEODE-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun resolved GEODE-4823.
----------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
> 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
> Fix For: 1.6.0
>
> 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)
