Thanks Andrew, Yes we generally do not leave any components in a "stopped" state. They're always "running/enabled/disabled". What we're hoping to do is utilize a "staging" environment for all changes as opposed to having to have any direct manipulation to the production clusters. Where the staging environment would then check-in changes to the registry... The production environment then recognized the pg isn't utilizing the newest available version and we can then tell the production environment to check in the latest version. As it stands today if the change that I checked in is aa new component in a flow, the new component that the production environment checks-in is in a stopped state. This then requires additional manual intervention to "enable/start" the flow.
I can see it potentially being a precautionary type thing... but would definitely be useful to have the option to have components retain status/state when checked into the registry. I imagined it would be somewhat similar to how MiNiFi works where components are assumed to be running at all times... at least I think that's how it's working in the background? On 2021/07/01 21:34:52, Andrew Grande <apere...@gmail.com> wrote: > Isn't the proper state for this use case enabled/disabled? NiFi will start > a PG and every schedulable component in it. If one needs to prevent this, > disable a processor. > > Andrew > > On Thu, Jul 1, 2021, 2:17 PM Phillip Lord <phillip.l...@onyxpoint.com> > wrote: > > > Hello, > > > > My organization is considering utilizing the Registry. From my testing it > > appears that versioning doesn't keep track of the state of components > > (stopped/started/etc). Is this accurate? Are there plans to have > > versioning keep track of this in future releases? > > > > I'm using NiFi 1.11.4 and Registry version 0.8.0 > > > > Thanks, > > Phil Lord > > >
