Georg Expanding on where I think Andrew was going...
With the NiFi 1.5.0 release and the associated NiFi Registry release you can now do this in a really powerful way. You can now create an 'Error Handling' flow which you can version control in the nifi registry. You can then use this versioned flow in as many places as you need in your NiFi instance connected to that registry. You can tweak/tune how you do error handling to improve it over time and publish new version of it back to the registry. You can then update your instances of those versioned flows that you're using to keep things well up to date. We'll work to support automatic version upgrades and other cool/obvious next steps but the registry now should get you well underway. Thanks On Mon, Feb 19, 2018 at 4:52 PM, Andrew Grande <[email protected]> wrote: > A Processing Group would serve as a reusable unit, which then has version > control applied to it. You would model your flows to abstract interactions > with e.g. in/output port objects. > > They also mentioned that nested PG can be versioned separately, looks like > git submodules behavior, but I haven't tried multi-level versioned PGs yet. > > Andrew > > > On Mon, Feb 19, 2018, 4:46 PM Georg Heiler <[email protected]> > wrote: >> >> How can I modularize and reuse parts of my nifi flows? >> I.e. Have a shared logging and error handling strategy which can be >> centrally configureed for all processor groups. >> >> Best Georg
