[
https://issues.apache.org/jira/browse/NIFI-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043827#comment-16043827
]
ASF GitHub Bot commented on NIFI-4043:
--------------------------------------
Github user bbende commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1901#discussion_r121037053
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/WaitNotifyProtocol.java
---
@@ -144,6 +150,28 @@ public void setReleasableCount(int releasableCount) {
}
+ /**
+ * Class to pass around the signal with the JSON that was deserialized
to create it.
+ */
+ public static class SignalHolder {
--- End diff --
Agreed, we can definitely get right of the SignalHolder if you use the
approach above.
> 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)
