[NIFI-5695] Connections to/from child groups' ports get confused when importing flow from Flow Registry

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.8.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 12/Oct/18 19:23
• Updated: 12/Oct/18 20:28
• Resolved: 12/Oct/18 20:28

Description

To replicate, create a Process Group with the following components:

InputPort -> LogAttribute -> OutputPort

Then move to the higher group and add this to Version Control.

Next, import another copy of the same group.

Connect the first child group's OutputPort to the second group's InputPort.

Add a GenerateFlowFile and connect it to the first group's Input Port.

Add a LogAttribute and connect the second group's OutputPort to it.

Now, version control the outer group.

At this point, all should behave as expected.

Now, if you import a second copy of the outer group, the newly imported group has connections going to/from the wrong ports. It appears that NiFi is not properly mapping a port in a child group to the appropriate child group if there are multiple copies of the (independently versioned) child group.

Issue Links

• links to: GitHub Pull Request #3070