Well we will be deploy Nifi in a docker container and need to configure everything at the time of the container’s creation and startup.
To be specific I’m using DistributedMapCacheService with a DetectDuplicate process to track whether a flowfile with a same attribute value had been already created in the last 10 minutes. If so abandon the new flowfile. I guess the thin I liked about the DistributedMapCacheService is that it already exists in NiFi, no additional installation required. From: Mike Thomsen <mikerthom...@gmail.com> Sent: Tuesday, January 14, 2020 7:42 PM To: users@nifi.apache.org Subject: Re: DistributedMapCacheService - automated creation [CAUTION: This email originated from outside of Kodak Alaris. Do not click links or open attachments unless you recognize the sender and know the content is safe.] ________________________________ What is your use case? Because this sounds vaguely like something that you could implement implicitly with the HBase version by just creating one big cache table with an eye for not overlapping column qualifiers and possibly liberal use of HBase TTLs. On Tue, Jan 14, 2020 at 6:04 PM William Gosse <william.go...@aifoundry.com<mailto:william.go...@aifoundry.com>> wrote: Is there any way to automate the creation of a DistributedMapCacheService I was hoping I could do this via a template but it doesn’t to get exported the way the DistributedMapCacheClientService does. The client got created just fine but there’s no service. I don’t see away to do this with restful api either. Any help would be greatly appreciated.
