You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Matt Gilman (JIRA)" <ji...@apache.org> on 2016/12/06 02:06:58 UTC

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

Matt Gilman created NIFI-3155:
---------------------------------

             Summary: 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
             Fix For: 1.2.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.3.4#6332)