And, for clarification, when a PG is imported from NiFi Registry, the initial state of non-disabled components is 'STOPPED'. It takes user interaction to put the components into a running state.
Agree with Andrew to disable (in the versioned flow in the Registry) any component which you do not want to start when starting the entire versioned flow, i.e. the Process Group level. -Mark On Thu, Jul 1, 2021 at 5:35 PM Andrew Grande <[email protected]> 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 <[email protected]> > 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 > > >
