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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on NIFI-3155:
-------------------------------------------------------

Commit 49285d325f9ec8fe687b513ee4d2146d99ef6579 in nifi's branch refs/heads/master from [~aldrin]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=49285d3 ]

NIFI-4719 - Incrementing Template encoding version to 1.2 to reflect changes incorporated in NIFI-3155

Signed-off-by: Pierre Villard <pi...@gmail.com>

This closes #2357.


> 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)