Yes Bryan, we developed process to deploy from registry uding nifi rest api.
I see so state is physically related to processors uuid. 1. when importing templates, the uuids change. so reading your suggestion hi jts that deploying from registry the same PG same or newer version (where our state processor remains de same) via rest API it shall keep uuids in both deploys is it? 2. where do processor states get stored physically at cluster and at locsl level? I suppose processors use internally the so called "zoo keeper" to also maintain states ? Additionally are just "state" files get synced in between nodes or are there nifi or zookeeper or some other type of apis being used? 3. Yesterday we had a flow using ListHdfs + FetchHdfs+ PutS3 , with ListHdfs using internal state management (that is property "Distributed Cache Service" is not set, i think this means processor using default nifi internal state system which is managed/implemented by zookeeper?). Something strange happened that dedpite 1000's files got pulled/stored in s3 but rightclicking ListHdfs state was empty.. there was no key/values on the list.. the processor was been running for 2 days. Isnt supposed for us to be able to inspect state? What could we do next time to troubleshoot this? Thanks in advance, Emanuel O. On Fri 7 Feb 2020, 21:54 Bryan Bende, <[email protected]> wrote: > Hello, > > How are you upgrading the flow? > > If you mean using NiFi Registry and selecting Change Version to a new > version, then yes it will retain state. > > Other than that, probably not because the state is tied to the UUID of > the processor, so if you used templates or some other approach, you > will likely get a new UUID for the processor in the new flow. > > Thanks, > > Bryan > > On Fri, Feb 7, 2020 at 4:44 PM Emanuel Oliveira <[email protected]> > wrote: > > > > Hi, > > > > I wonder.. Is it possible to upgrade PG flow to new version when its > contains processors using state ? > > FYI The new flow using exact same processors/versions its just minor > tweaks on some properties etc.. > > > > Best Regards, > > Emanuel Oliveira > > >
