[
https://issues.apache.org/jira/browse/NIFI-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904430#comment-14904430
]
ASF GitHub Bot commented on NIFI-988:
-------------------------------------
GitHub user joemeszaros opened a pull request:
https://github.com/apache/nifi/pull/92
NIFI-988: PutDistributedMapCache processor
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.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ImpressTV/nifi NIFI-988
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/92.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #92
----
commit 6b1328f3f181a27a5856d26983ed3329ee317522
Author: Joe <[email protected]>
Date: 2015-09-23T11:16:02Z
NIFI-988: PutDisributedMapCache processor implementation
commit ee7d89cb01d4661cfff2c4f0d093e38758680a56
Author: Joe <[email protected]>
Date: 2015-09-23T12:32:37Z
NIFI-988: Test cases for PutDistributedMapCache
----
> 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)
