You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Charlie Black (JIRA)" <ji...@apache.org> on 2018/02/01 20:14:00 UTC

[jira] [Commented] (GEODE-2932) Users would like option for PR with empty data policy

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

Charlie Black commented on GEODE-2932:
--------------------------------------

This would simplify the streaming uses cases where I would kick off a work stream for co-located data operations.   

> Users would like option for PR with empty data policy 
> ------------------------------------------------------
>
>                 Key: GEODE-2932
>                 URL: https://issues.apache.org/jira/browse/GEODE-2932
>             Project: Geode
>          Issue Type: Improvement
>          Components: regions
>            Reporter: Fred Krone
>            Priority: Major
>              Labels: storage_2
>
> Allow for accessor partitioned regions to route incoming operations. 
> The idea is to use a PR to control distributed/partitioned _processing_ of events without the need to cache them. This option would be especially useful for streaming cases where the target is a PR's attached AsyncEventQueue.  Also useful when the target is a PR's attached CacheListener.  We have developed some work-around for this in the field, but they require significant code and complex configuration, and limited to event input from peer-clients.
> For many use-cases, there would still be a need to co-locate other standard/caching PR's with the "empty" one to enable enrichment, transformation, and similar logic in the custom event callbacks (either CacheListener or AEQ Listener). 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)