NIFI-14874 Unable to move destination of a Connection to a Process Group when source component is running

[alepekhin]

Summary

NIFI-14874

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

• Apache NiFi Jira issue created

Pull Request Tracking

• Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-14874
• Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-14874

Pull Request Formatting

• Pull Request based on current revision of the main branch
• Pull Request refers to a feature branch with one commit containing changes

Verification

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 should allow to edit connection and select input port

Build

• Build completed using ./mvnw clean install -P contrib-check
  • JDK 21

Licensing

• New dependencies are compatible with the Apache License 2.0 according to the License Policy
• New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

• Documentation formatting appears as expected in rendered files

[joewitt]

I am pretty sure the solution here wont simply be to not check whether the change is valid on the server side.

There are some important reasons we would not want to change the target in the midst of processing and thus why we enforce this.

[alepekhin]

@joewitt We have discussed it in the issue. We do change target when we move connection to another target Process. Why we can not do the same when we move connection to another Input Port?