You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/03/13 07:09:00 UTC

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

     [ https://issues.apache.org/jira/browse/GEODE-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated GEODE-4823:
----------------------------------
    Labels: pull-request-available  (was: )

> 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
>
> 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)