Hi Yari,
The concept you are looking for has been discussed a bit and a draft
feature proposal was created for referenceable process groups [1], although
is a common pattern and implementable with the current functionality
provided; common cases of this are standard tagging or enrichment sets of
functionality.
What you want to attempt seems like you wouldn't necessarily need to do an
RPG (unless you were looking to cut down on connection clutter), but could
perform routing to a single process group via attributes and tagging and
then using a fan out to send data back to its respective group.
Flow of data would be something such as:
* Source Group {A, B, ...}
* Update Attribute
- Tag Data as Source Group {A, B, ...} (source)
* Singleton Process group input port for common processing
* Route on Attribute (source)
- Create relationships for each of the groups that are transmitting data
to this common block
* Source Group
[1]
https://cwiki.apache.org/confluence/display/NIFI/Reference-able+Process+Groups
On Tue, Dec 27, 2016 at 9:49 AM, Yari Marchetti <
[email protected]> wrote:
> Hello,
> we're actively using Nifi on production but there's a recurring problem
> popping out every now and then: maintenance of process groups created from
> templates, as we're spending quite some time looking for all the instances
> of a specific template and updating them as required.
>
> What we would like to do it's something like a singleton instance of a
> process group that could just be referenced by all other the flows in Nifi
> without having different instances of a template. Is there any way to
> achieve this? The only thing that came to my mind is using a RPG to the
> local cluster (which it's made up of 3 servers), don't know though if it
> would work...
>
> Thanks,
> Yari
>
