[NIFI-6108] Port names in nested PGs get changed when importing from Registry

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9.0
• Fix Version/s: 1.10.0, 1.9.1
• Component/s: Flow Versioning
• Assignee: Kevin Doran
• Reporter: Kevin Doran
• Created: 06/Mar/19 21:22
• Updated: 29/Mar/19 15:06
• Resolved: 06/Mar/19 22:08

Description

When importing a versioned process group from NiFi Flow Registry to the canvas, if the versioned process group contains nested (unversioned) process groups, any 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.

Issue Links

• is duplicated by: NIFIREG-243 Impossible to use previous flow version
• is related to: NIFI-5950 Error updating flow version if a port is removed and another port is given the deleted port's name
• links to: GitHub Pull Request #3356