Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1117#discussion_r84139791
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/nf-processor-details.js
---
@@ -185,6 +191,19 @@ nf.ProcessorDetails = (function () {
$('#read-only-run-schedule').hide();
}
+ // only show the execution-node when applicable
+ if (executionNode === 'ALL') {
+ executionNode = "All nodes";
+ } else if (executionNode === 'PRIMARY') {
+ executionNode = "Primary node only";
+ }
+ nf.Common.populateField('read-only-execution-node',
executionNode);
+ if (nf.Canvas.isClustered()) {
--- End diff --
Same comment as above regarding determining whether or not we should be
showing the execution node. Since a node can be easily connected/disconnected
we should probably show the execution node if clustered or if the value is
'primary node only'. Should only be hiding this field if the instance is not
clustered and the execution node is 'all'.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
