[
https://issues.apache.org/jira/browse/NIFI-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648418#comment-16648418
]
ASF subversion and git services commented on NIFI-5695:
-------------------------------------------------------
Commit 270ce8570df7a00a26f431d8d8ae0245b898bf69 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=270ce85 ]
NIFI-5695: Fixed bug that caused ports to not properly map to their correct
child group on Flow Import if the child group is independently versioned
This closes #3070.
Signed-off-by: Bryan Bende <bbe...@apache.org>
> Connections to/from child groups' ports get confused when importing flow from
> Flow Registry
> -------------------------------------------------------------------------------------------
>
> Key: NIFI-5695
> URL: https://issues.apache.org/jira/browse/NIFI-5695
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 1.8.0
>
> Attachments: Group-After-Import.png, Original-Group.png
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
