Eduardo Using the programming language analogy consider that a given PG on the flow is both the function definition and the call-stack/state. In flow terms then it is both the flow definition and the data at various points in the flow.
A great way to handle what you want to do is to use versioned flows. Publish your PG as a versioned flow to the nifi registry. Then put instances of that PG wherever you need it. This way you can update the definition of your versioned flow and opt in to when all the instances of it change their version. Thanks On Thu, Nov 5, 2020 at 12:16 PM Mike Thomsen <[email protected]> wrote: > You could mix funnels together to bring the various upstream > components together in a way that's easier to visually manage. Other > than that, I think treating it like a function and not wiring it up to > those other PGs would fundamentally break the behavior of NiFi. > > On Thu, Nov 5, 2020 at 1:26 PM Eduardo Fontes <[email protected]> > wrote: > > > > Hi all, > > > > I am thinking about how I can reuse flows (PGs) through all other flows > in > > the same NiFi cluster. > > > > Using Input/Output ports is very bad for dozens of flows. The layout of > the > > main flow will be a mess. > > > > There is some feature to use a PG like a function (in any program > language)? > > > > Regards, > > Eduardo Fontes >
