[jira] [Commented] (NIFI-8261) When changing flow version, can silently fail to update connections connected to Output Ports

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-8261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291115#comment-17291115 ] 

ASF subversion and git services commented on NIFI-8261:
-------------------------------------------------------

Commit 82eedea659a08581f21d31c6dc4516d615b25e37 in nifi's branch refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=82eedea ]

NIFI-8261: When gathering the states of affected components, make sure that we properly obtain the state of Input Ports and Output Ports

Signed-off-by: Pierre Villard <pi...@gmail.com>

This closes #4844.


> When changing flow version, can silently fail to update connections connected to Output Ports
> ---------------------------------------------------------------------------------------------
>
>                 Key: NIFI-8261
>                 URL: https://issues.apache.org/jira/browse/NIFI-8261
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.14.0, 1.13.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> If I try to change the version of a dataflow from Version 1 to Version 2, and the changes result in a connection being removed or its destination changing, all is OK If the destination is not an Output Port. However if the destination of the connection in the current version is an Output Port, and the Output Port is running, the connection will not be updated. The logs will show no errors, and the UI will either indicate that the connection couldn't be updated because the destination is running, or it will claim that the update was successful (depending on the situation). But in either case, the flow will not have been updated properly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)