Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 08-03-2018 08:06 AM
Created 08-03-2018 03:12 PM
Currently, NiFi support for Redis is in the form of the RedisDistributedMapCacheClientService, so you can use FetchDistributedMapCache and PutDistributedMapCache to get data in and out of Redis. Check the documentation for the Redis service as it may not use the same directives as you were expecting, so I'm not sure if this will be sufficient for your use case or not.
An alternative is to use a scripting processor such as ExecuteScript or InvokeScriptedProcessor, you can point the Module Directory property to the Redis client JARs and basically write your own "mini-processor" in a language like Groovy or Jython to interact with Redis how you wish.
Created 08-03-2018 03:12 PM
Currently, NiFi support for Redis is in the form of the RedisDistributedMapCacheClientService, so you can use FetchDistributedMapCache and PutDistributedMapCache to get data in and out of Redis. Check the documentation for the Redis service as it may not use the same directives as you were expecting, so I'm not sure if this will be sufficient for your use case or not.
An alternative is to use a scripting processor such as ExecuteScript or InvokeScriptedProcessor, you can point the Module Directory property to the Redis client JARs and basically write your own "mini-processor" in a language like Groovy or Jython to interact with Redis how you wish.
Created 12-21-2018 07:35 PM
You can try the processor I've implemented
https://github.com/javajefe/nifi-redis-pubsub-bundle
Any feedback is appreciated