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

Mark Bean commented on NIFI-14874:
----------------------------------

[~alex1947] Thanks for the update. I stand corrected and updated the 
description. In NiFi 1.28.1, the behavior is similar in that the connection 
cannot be relocated to the process group's input port. 

So, the behavior is consistent across versions. I still believe it is 
incorrect. Is there a reason why an input port should be treated differently 
than a processor in terms of relocating a connection's destination?

> Unable to move destination of a Connection to a Process Group when source 
> component is running
> ----------------------------------------------------------------------------------------------
>
>                 Key: NIFI-14874
>                 URL: https://issues.apache.org/jira/browse/NIFI-14874
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Mark Bean
>            Priority: Major
>
> The destination of a Connection is unable to be changed if the source of the 
> Connection is running, the current destination is not running, and the new 
> destination is an Input Port (either a Local Port in a Process Group or a 
> Remote Port in a Remote Process Group.)
> This would be expected behavior if the destination were running, but not 
> expected if it is not running. Case in point: The destination can be changed 
> from one processor to another even with the source running. It just does not 
> work to change the destination to an Input Port.
> To reproduce, create any two processors, Processor A and Processor B, with a 
> Connection from Processor A (source) to Processor B (destination.) Also, 
> create a Process Group which contains an Input Port within it. Start 
> Processor A.
> Attempt to move the destination of the Connection from Processor B to the 
> Process Group's Input Port. It fails. 
> Add a third Processor, Processor C. Attempt to move the destination of the 
> Connection from Processor B to Processor C. It succeeds.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to