[
https://issues.apache.org/jira/browse/NIFI-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967247#comment-14967247
]
ASF subversion and git services commented on NIFI-988:
------------------------------------------------------
Commit 97441ea0c23ebdc7c51939ff28ba270012c0fe55 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=97441ea ]
Merge branch 'NIFI-988' of https://github.com/ImpressTV/nifi into NIFI-988
> 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)
