[
https://issues.apache.org/jira/browse/NIFI-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043840#comment-16043840
]
ASF GitHub Bot commented on NIFI-4043:
--------------------------------------
Github user ijokarumawak commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1901#discussion_r121038362
--- Diff:
nifi-nar-bundles/nifi-standard-services/nifi-distributed-cache-client-service-api/src/main/java/org/apache/nifi/distributed/cache/client/AtomicDistributedMapCacheClient.java
---
@@ -71,6 +73,23 @@
* @return true only if the key is replaced.
* @throws IOException if unable to communicate with the remote
instance
*/
+ @Deprecated
<K, V> boolean replace(K key, V value, Serializer<K> keySerializer,
Serializer<V> valueSerializer, long revision) throws IOException;
--- End diff --
@bbende Yeah, actually, I'm writing Proof of Concept code and it will be
ready in next few hours hopefully. I will share it on Github later so that you
can take a look, if it looks ok, then lets update the
AtomicDistributedMapCacheClient in another JIRA so that both of your Redis
cache and my Couchbase cache can use it.
I found another benefit of this approach,, we may not have to add new
protocol version. I'm testing the idea now.
> Implement a DistributedMapCacheClient backed by Redis
> -----------------------------------------------------
>
> Key: NIFI-4043
> URL: https://issues.apache.org/jira/browse/NIFI-4043
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
>
> We should provide other caching options besides the
> DistributedMapCacheClient/DistributedMapCacheServer.
> Redis is a popular caching solution and we could implement a
> RedisDistributedMapCacheClient that would let us use all the existing
> processors against Redis.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
