You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2016/03/25 00:14:25 UTC
[jira] [Updated] (GEODE-915) invalidate event when entry does not
exist or already invalid
[ https://issues.apache.org/jira/browse/GEODE-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darrel Schneider updated GEODE-915:
-----------------------------------
Component/s: (was: core)
regions
> 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: regions
> 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)