geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-915) invalidate event when entry does not exist or already invalid
Date Fri, 05 Feb 2016 17:02:40 GMT


ASF subversion and git services commented on GEODE-915:

Commit f3dd3353deb154ade18136781cc18308d3f615dd in incubator-geode's branch refs/heads/develop
from [~dschneider]
[;h=f3dd335 ]


If the system property gemfire.FORCE_INVALIDATE_EVENT
is set to true then afterInvalidate on CacheListeners will be called even
if the entry does not exist or if the entry is already invalid.

> invalidate event when entry does not exist or already invalid
> -------------------------------------------------------------
>                 Key: GEODE-915
>                 URL:
>             Project: Geode
>          Issue Type: New Feature
>          Components: core
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
> 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

View raw message