[
https://issues.apache.org/jira/browse/NIFI-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249995#comment-16249995
]
ASF subversion and git services commented on NIFI-3155:
-------------------------------------------------------
Commit 2d3e5abf81d5fa70cd6efd60644755b51c785369 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=2d3e5ab ]
NIFI-3155, NIFI-4571: Fix issue of Remote Group Port having ID the same as on
the remote system, by adding an additional targetId field RemoteGroupPort's;
this also fixes issue of stats being mixed together for RPG's with the same
URL. This closes #2253
> 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
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 1.5.0
>
>
> 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)
