[
https://issues.apache.org/jira/browse/NIFI-9825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard resolved NIFI-9825.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the
1.x release line. Marking as resolved as part of a cleanup operation. Please
open a new one with an updated description if this is still relevant for NiFi
2.x.
> Execution "Primary node" with incoming connections limitation bug
> -----------------------------------------------------------------
>
> Key: NIFI-9825
> URL: https://issues.apache.org/jira/browse/NIFI-9825
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.15.3
> Reporter: Josef Zahner
> Priority: Major
> Labels: ExecuteSQL, primary
> Attachments: Screenshot 2022-03-23 at 13.53.52.png
>
>
> Somewhen in the past an information for users has been added that if a
> processor can have incoming connections, NiFi prevents the user to set
> execution to "Primary node" only. In theory this is fine, but the problem is,
> the "ExecuteSQL" processor can run with or without incoming connections.
> I'm using the processor on a cluster without incoming connections, but I
> never wanna execute the same query on all cluster nodes and it's
> uncomfortable to set a "GenerateFlowFile" processor with "Primary only"
> execution mode in front of the "ExecuteSQL". At the moment I can't set the
> "ExecuteSQL" to "Primary node" only without a *connected* incoming connection
> as NiFi generates the error message "{_}'Execution Node' is invalid because
> Processors with incoming connections cannot be scheduled for Primary Node
> only{_}". Please check my screenshot.
> NiFi should not check for the possibility on the processor for incoming
> connections but for real connected connections. Thanks
> !Screenshot 2022-03-23 at 13.53.52.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
