[
https://issues.apache.org/jira/browse/NIFI-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358935#comment-16358935
]
ASF subversion and git services commented on NIFI-4863:
-------------------------------------------------------
Commit 61c6f0305bc7b5c68456fc2d40e0536698821c47 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=61c6f03 ]
NIFI-4863: Bug fixes to the way that we handled Remote Group Ports when
changing flow version / reverting local changes
- Everywhere that we ignore adding remote ports we should ignore removing
remote ports as well in flow diffs
This closes #2462.
Signed-off-by: Bryan Bende <[email protected]>
> If changing version of flow and new flow has no connection to RPG Port, can
> get error saying unable to start components
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-4863
> URL: https://issues.apache.org/jira/browse/NIFI-4863
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.5.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.6.0
>
>
> When we have a Remote Process Group with multiple ports, we push to the flow
> registry the ports that we have connections for. I have a connection to Port
> A and save that to the flow registry, then create a connection to Port B. I
> have RPG transmitting data. Then I revert local changes. This properly
> reverts the flow but fails to restart components. This is because it is
> attempting to start Port B, and there are no connections for that Port.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
