Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2509#discussion_r181149446
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-processor-configuration.js
---
@@ -741,8 +742,8 @@
}
});
- // show the execution node option if we're cluster or
we're currently configured to run on the primary node only
- if (nfClusterSummary.isClustered() || executionNode
=== 'PRIMARY') {
+ // show the execution node option if we're clustered
and execution node is not restricted to run only in primary node
+ if (nfClusterSummary.isClustered() &&
executionNodeRestricted !== true) {
--- End diff --
How does this work in the case where the Processor previously did not have
`executionNodeRestricted` and the `executionNode` was `ALL`?
I'm wondering if we shouldn't be hiding this field in these scenarios.
Currently, if you're not clustered and the value is `PRIMARY` we show the field
but we disable the Primary options. Please refer to `getExecutionNodeOptions`
in nf-processor-configuration.js. I think the scenario I described above is
equivalent. If the existing value of `executionNode` was `ALL` we would want to
render that but disable that option as a choice.
---
