Mike Thomsen did some work for a cassandra backing of DistributedMapCache:
https://issues.apache.org/jira/browse/NIFI-7821 <https://issues.apache.org/jira/browse/NIFI-7821> I am excited to see this coming in 1.13 and I will be using it on a few use cases here with both Cassandra and Astra (cassandra as a service). Steven Matison | Data Architect | datastax.com > On Feb 15, 2021, at 3:00 AM, Pierre Villard <pierre.villard...@gmail.com> > wrote: > > There will be an Hazelcast implementation (embedded into NiFi) that will be > released with NiFi 1.13. It comes with some limitations that you need to be > aware of (example: the data is not persisted in case of a cluster restart) > but I believe all of this is documented in the "additional details" of the > new controller services. > > Thanks, > Pierre > > Le ven. 12 févr. 2021 à 19:21, Jorge Machado <jom...@me.com > <mailto:jom...@me.com>> a écrit : > Thanks to all ! > I was thinking about hazelcast hashmap > > >> On 12. Feb 2021, at 16:08, Chris Sampson <chris.samp...@naimuri.com >> <mailto:chris.samp...@naimuri.com>> wrote: >> >> I'm pretty sure they don't, you need to use an external implementation, such >> as Redis. >> >> The DistributedMapCacheServer is a reference implementation but there are >> alternatives - see the list of available implementations in the "Distributed >> Cache Service" property of the PutDistributedMapCache processor docs [1]. >> >> You can also implement your own by extending the DistributedCacheServer >> class. >> >> >> [1]: >> https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.12.1/org.apache.nifi.processors.standard.PutDistributedMapCache/index.html >> >> <https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.12.1/org.apache.nifi.processors.standard.PutDistributedMapCache/index.html> >> >> --- >> Chris Sampson >> IT Consultant >> chris.samp...@naimuri.com <mailto:chris.samp...@naimuri.com> >> >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.naimuri.com_&d=DwMFaQ&c=adz96Xi0w1RHqtPMowiL2g&r=9b4JGNGVLlVsvOzQx1rC-bAHtGhipOxa1b9yWNZZIKs&m=UNaBdCu09G0qwxYeEt5Oo3SNjs33xPkFWrkJt8MJfgg&s=aZKcot09GuZN4_KaInVQBKlinhhgyikxY4yy83BByt4&e=> >> >> >> On Fri, 12 Feb 2021 at 14:48, Jorge Machado <jom...@me.com >> <mailto:jom...@me.com>> wrote: >> Hey everyone, >> >> Is there any documentation on how to use DistributedCacheServer ? Currently >> from what I see this is single point of failure or does it really sync the >> data between nodes ? >> >> I want to have something similar to zookeeper state but not in zookeeper >> because it needs to be available between processors. My rough problem: >> >> >> Flow : >> >> * Start the flow and store a state (Similar to the QueryTable, which uses >> zookeeper to store the max row) >> * do some processing >> * update the state >> >> >> This needs to be reachable between servers of course. What I tested the >> DistributedMapCacheClientService needs a server to connect which I point to >> localhost. But if the entry that I need is on another server how do they >> sync the data ? >> >> Thx >
