[jira] [Commented] (NIFI-3155) Remote Group Port UUIDs

["Matt Gilman (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974575#comment-15974575 ] 

Matt Gilman commented on NIFI-3155:
-----------------------------------

Removed the fix version for lack of progress currently. Will re-assign when appropriate.

> 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.3.15#6346)