[
https://issues.apache.org/jira/browse/NIFI-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824314#comment-15824314
]
ASF subversion and git services commented on NIFI-3214:
-------------------------------------------------------
Commit ef54a8ec69b6b363eedd50944c48d5d013cf5ccc in nifi's branch
refs/heads/master from [~ijokarumawak]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=ef54a8e ]
NIFI-3214: Added fetch and replace to DistributedMapCache
- Using fetch and replace together can provide optimistic locking for
concurrency control.
- Added fetch to get cache entry with its meta data such as revision
number.
- Added replace to update cache only if it has not been updated.
- Added Map Cache protocol version 2 for those new operations.
- Existing operations such as get or put can work with protocol version
1.
This closes #1410.
Signed-off-by: Bryan Bende <[email protected]>
> Add a method to DistributedMapCacheClient to replace existing key only if it
> hasn't been changed
> ------------------------------------------------------------------------------------------------
>
> Key: NIFI-3214
> URL: https://issues.apache.org/jira/browse/NIFI-3214
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Bryan Bende
> Assignee: Koji Kawamura
>
> It would be helpful for some processors to be able to -get a list of all the
> keys in the distributed map cache that match some pattern, or even to get a
> list of all the keys. We should update DistributedMapCacheClient to have a
> method like getKeys(String pattern).- replace an existing key in the
> distributed map cache with concurrency control so that the key will be
> replaced only if it hasn't been updated by other operations since updating
> client program fetched the key.
> Updated JIRA description as mentioned in
> [NIFI-3216|https://issues.apache.org/jira/browse/NIFI-3216?focusedCommentId=15812535&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15812535].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
