[jira] [Commented] (GEODE-1209) Support/Propagating eviction and expiration operation with AsycEventQueue.

["Anilkumar Gingade (JIRA)" <ji...@apache.org>]

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

Anilkumar Gingade commented on GEODE-1209:
------------------------------------------

Found a critical product bug, that impacts this feature. Created a new product bug GEODE-1472.
Sent new proposal to community with supporting only expiration-destroy events for now.
After feedback from community started adding/modifying the changes to support forwarding expiration destroy events.

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