You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Kevin Doran (JIRA)" <ji...@apache.org> on 2019/03/06 21:23:00 UTC
[jira] [Created] (NIFI-6108) Port names in nested PGs get changed
when importing from Registry
Kevin Doran created NIFI-6108:
---------------------------------
Summary: Port names in nested PGs get changed when importing from Registry
Key: NIFI-6108
URL: https://issues.apache.org/jira/browse/NIFI-6108
Project: Apache NiFi
Issue Type: Bug
Components: Flow Versioning
Affects Versions: 1.9.0
Reporter: Kevin Doran
Assignee: Kevin Doran
Fix For: 1.10.0
When importing a versioned process group from NiFi Flow Registry to the canvas, if the versioned process group contains nested (unversioned) process groups, and input or output ports in the nested process group will be renamed upon import. The net result is that you end up with names that look like {{name (<port-uuid>)}} and that the process group shows that it is out of sync with Registry because of local changes.
*Workaround in affected versions: *manually rename any affected ports back to their correct names, i.e., remove the {{ (<port-uuid)}} portion.
For background, this bug got introduced in the fix for 5950 which was adding temporary name suffixes during flow updates to avoid name collision during the flow update sequence. If the port is in an unversioned, nested PG, the code that renames it to its final name will fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)