You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/01 13:38:27 UTC

[jira] [Commented] (NIFI-988) PutDistributedMapCache processor

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

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

Github user joemeszaros commented on the pull request:

    https://github.com/apache/nifi/pull/92#issuecomment-144703463
  
    I think your answer is related to an other pull request #94 (NIFI-989). Let me share my opinion there, not in this PutDistributedMapCache PR.


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