Hello We have this concept or a very similar concept documented here as a feature proposal. https://cwiki.apache.org/confluence/display/NIFI/Reference-able+Process+Groups It hasn't been worked on yet but will be a really cool thing. The basic gist is that you can create a process group that acts as a callable function which you can then place in one or many places on the flow. Ensures you only have one thing/place to maintain for some critical logic step and it is more efficient on the system from a threading pov.
We also have the concept of flow versioning https://cwiki.apache.org/confluence/display/NIFI/Configuration+Management+of+Flows which may also offer a similar behavior except it would be more like you described originally in that there would actually be multiple instances of that group but with it being versioned the other instances can be easily kept in sync. Thanks Joe On Thu, Mar 9, 2017 at 7:01 AM, James McMahon <jsmcmah...@gmail.com> wrote: > I am happy to do this Oleg. Thank you very much for your reply. > > Cheers, > > Jim > > On Thu, Mar 9, 2017 at 6:56 AM, Oleg Zhurakousky > <ozhurakou...@hortonworks.com> wrote: >> >> Jim >> >> I see where you’re going with this and I do believe that it is a valuable >> enterprise feature. Unfortunately, template XML files are not the bootstrap >> source of the flow such as flow.gz file. They are only used for >> save/move/migrate/etc., which means any modifications to them are not going >> to be automatically picked up. >> But as I said, I do personally believe that something like this would be >> extremely valuable and could potentially be put on NiFi roadmap. Would you >> mind raising a Feature Request - https://issues.apache.org/jira/browse/NIFI >> so we can at least track it and gage the public interest? >> >> Cheers >> Oleg >> >> > On Mar 9, 2017, at 6:46 AM, James McMahon <jsmcmah...@gmail.com> wrote: >> > >> > Good morning. We are developing NiFi workflows with a few key strategic >> > goals in mind, one of which is this: change common workflows in one place >> > only, and have those changes ripple through to all process groups that >> > employ that code. >> > >> > More specifically: we have a complex but common workflow that we save as >> > template XYZ. That template is used within Process Group ABC, DEF, and XYZ. >> > We need to make improvements to the template, and want those improvements >> > to >> > be picked up automatically by each of the process groups. How do we make >> > that happen? >> > >> > Thank you in advance for your insights. >> > >> > Jim >> >
