geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1209) Support/Propagating eviction and expiration operation with AsycEventQueue.
Date Fri, 20 May 2016 16:30:13 GMT

    [ https://issues.apache.org/jira/browse/GEODE-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293654#comment-15293654
] 

ASF subversion and git services commented on GEODE-1209:
--------------------------------------------------------

Commit 46056a6611970c06ab1414900e35e4135533af87 in incubator-geode's branch refs/heads/feature/GEODE-835-test
from [~agingade]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=46056a6 ]

GEODE-1209: Added new attribute to forward eviction/expiration to AEQ.
Following changes are made:
1. Added new attribue/flag to forward eviction and expiration destroy events.
2. Added new option in CreateAsyncEventQueue Gfsh command. Also cleaned up arguments for create
AEQ function invoked by gfsh. Instead of object array the args are wrapped in args object.


> Support/Propagating eviction and expiration operation with AsycEventQueue.
> --------------------------------------------------------------------------
>
>                 Key: GEODE-1209
>                 URL: https://issues.apache.org/jira/browse/GEODE-1209
>             Project: Geode
>          Issue Type: Bug
>          Components: docs, wan
>            Reporter: Anilkumar Gingade
>
> The AsyncEventQueue works as a write-behind cache event handler to synchronize region
updates with other source...Currently it does not support distribution of eviction or expiration
operation....This makes the external source to be out of sync with data that has been removed/invalidated
through eviction and expiration.
> This ticket is to add/support eviction and expiration operation with AsyncEventQueue,
so that all the operations are propagated to AsyncEventQueueListener and the usage of those
events are left to underlying implementation/applications(like WAN, Lucene, plug-able storage,
etc).
> http://gemfire.docs.pivotal.io/docs-gemfire/latest/developing/events/implementing_write_behind_event_handler.html#implementing_write_behind_cache_event_handling



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

Mime
View raw message