nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-988) PutDistributedMapCache processor
Date Wed, 23 Sep 2015 15:59:04 GMT

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

ASF GitHub Bot commented on NIFI-988:
-------------------------------------

Github user markap14 commented on the pull request:

    https://github.com/apache/nifi/pull/92#issuecomment-142647457
  
    @joemeszaros Can you explain the use case here a little bit more? The DistributedMapCache
services were originally developed in order to be used in the DetectDuplicate processor. It
has since found a couple of other uses. I'm trying to envision how the PutDistributedMapCache
processors might be used.
    
    Thanks
    -Mark


> PutDistributedMapCache processor
> --------------------------------
>
>                 Key: NIFI-988
>                 URL: https://issues.apache.org/jira/browse/NIFI-988
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core Framework
>            Reporter: Joe Mészáros
>            Priority: Minor
>              Labels: cache, distributed, feature, new, put
>
> There is a standard controller service, called DistributedMapCacheServer, which provides
a distributed cache, and an associated DistributedMapCacheClientService to interact with the
cache. But there is not any standard processor, which puts data into the cache, and helps
the user to leverage the distributed cache capabilities.
> The purpose of PutDistributedMapCache is very similar to the egress processors: it gets
the content of a FlowFile and puts it to a distributed map cache, using a cache key computed
from FlowFile attributes. If the cache already contains the entry and the cache update strategy
is 'keep original' the entry is not replaced.



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

Mime
View raw message