Ryan, If you're running 1.7 or later you can enable or disable in bulk just like you can start or stop. It's supported right in NiFi UI. You can use actions out of the Operate palette or the context menu.
https://issues.apache.org/jira/browse/NIFI-5066 Matt On Wed, Mar 27, 2019 at 2:07 PM Andy LoPresto <[email protected]> wrote: > Ryan, > > Reading through your email, my immediate suggestion was NiPyAPI. I think > Dan has wrapped some useful query methods there that could make this quite > easy. Obviously you are aware of it, but it’s still my best recommendation > for now. > > > Andy LoPresto > [email protected] > *[email protected] <[email protected]>* > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > > On Mar 27, 2019, at 10:58 AM, Ryan H <[email protected]> > wrote: > > Hi All, > > Is there a good way to change all processors on the canvas that are > stopped to a disabled state instead? The problem is that we have a large > amount of processors on our canvas that are in the stopped state which is > killing the UI performance (wouldn't want to go to each of the 2,000 > stopped processors individually and mark as disabled). We just learned that > this isn't an issue (with regard to UI performance) when processors are in > the disabled state due to the way status checks are performed. I'm sure > this could be scripted with NiPy or something else, but just wanted to > throw the question out to the community first before delving into this. > > Cheers, > > Ryan H > > >
