[
https://issues.apache.org/jira/browse/NIFI-6108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786171#comment-16786171
]
ASF subversion and git services commented on NIFI-6108:
-------------------------------------------------------
Commit 1d06044e3b08a886c6d8990ce5bfaa69e63d7324 in nifi's branch
refs/heads/master from Kevin Doran
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1d06044 ]
NIFI-6108: Fix port names when imported from registry
This closes #3356.
Signed-off-by: Bryan Bende <[email protected]>
> 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
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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 NIFI-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)
