[
https://issues.apache.org/jira/browse/NIFI-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904987#comment-14904987
]
ASF GitHub Bot commented on NIFI-988:
-------------------------------------
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/92#issuecomment-142689586
OK so to make sure that I am understanding the use case. The idea is just
to use this processor to put data into this cache, so that other custom
processors can access the data in the cache using the distributed cache
controller service, correct?
The only concern that I might have here is the amount of Java heap that
would be used up by this cache, holding the contents of FlowFiles in the cache.
> 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)
