geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darrel Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GEODE-915) invalidate event when entry does not exist or already invalid
Date Fri, 05 Feb 2016 17:03:39 GMT

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

Darrel Schneider resolved GEODE-915.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0-incubating.M2

> invalidate event when entry does not exist or already invalid
> -------------------------------------------------------------
>
>                 Key: GEODE-915
>                 URL: https://issues.apache.org/jira/browse/GEODE-915
>             Project: Geode
>          Issue Type: New Feature
>          Components: core
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>             Fix For: 1.0.0-incubating.M2
>
>
> When a Region invalidate finds that the entry does not exist or is already invalid it
does not invoke afterInvalidate on the CacheListener. Some users have requested that afterInvalidate
be invoked even in these cases.
> What was done to for them was a system property named "gemfire.FORCE_INVALIDATE_EVENT"
was added. If it was set to "true" then afterInvalidate was invoked even if the entry did
not exist or was already invalid. In both these cases the oldValue on the EntryEvent passed
to afterInvalidate was set to null.



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

Mime
View raw message