[
https://issues.apache.org/jira/browse/NIFI-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16206103#comment-16206103
]
Matt Gilman commented on NIFI-3155:
-----------------------------------
[~randy_b] Sorry, I missed your comment/question from earlier. RPGs can be used
load balance data across a cluster. This is still the preferred approach. This
JIRA is to address a concern that will become more relevant with the ongoing
SDLC and Registry efforts.
[~kislayosho] Thanks for your interest in contributing to NiFi. This JIRA may
not be the best candidate as an entry point for a new contributor given the
nature of the issue within the core framework and the cross-cutting concerns of
its implications (SDLC, provenance, security, etc). I believe there is a JIRA
label for issues may be good candidates for new contributors (look for beginner
or newbie). Another option may be to look at an issue or improvement to a
component or feature you've used personally. Also, check out the contributor
guide [1] if you haven't already.
[1] https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide
> Remote Group Port UUIDs
> -----------------------
>
> Key: NIFI-3155
> URL: https://issues.apache.org/jira/browse/NIFI-3155
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Priority: Critical
>
> Remote Group Ports assume the UUID of the port on the target instance. This
> is critical for retaining which port the connection is associated with.
> However, this is problematic for any flow which contains multiple RPGs
> pointed to the same target instance. Associating the underlying component
> when only an ID is known (ie provenance) is impossible as the UUID is
> ambiguous.
> This issue also exists for self-referencing RPGs but is mitigated with extra
> logic around these troublesome scenarios. For instance, we can differentiate
> the Remote Group Port from the Root Group Port of a self-referencing RPG by
> looking at the component type. However, this isn't possible with multiple
> RPGs referencing the same target instance.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
