[
https://issues.apache.org/jira/browse/NIFI-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589609#comment-15589609
]
ASF GitHub Bot commented on NIFI-401:
-------------------------------------
Github user mcgilman commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1117#discussion_r84138137
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-processor-configuration.js
---
@@ -662,6 +674,16 @@ nf.ProcessorConfiguration = (function () {
}
});
+ // select the execution node
+ $('#execution-node-combo').combo('setSelectedOption', {
+ value: executionNode
+ });
+ if (nf.Canvas.isClustered()) {
--- End diff --
If we are going to hide/show the execution node container, we should
probably also be considering the currently configured value. If a node is
configured for 'Primary Node Only' we need to retain that fact even when not
clustered. If a user has disconnected a node and then went to that node
directly we still want the configuration actually reflected. Should probably
show the field if clustered or if the execution node is 'primary node only'.
> New Scheduling strategy (On primary node - CRON )
> -------------------------------------------------
>
> Key: NIFI-401
> URL: https://issues.apache.org/jira/browse/NIFI-401
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Matthew Clarke
> Priority: Minor
> Attachments: initial prototype .png
>
>
> Currently the only scheduling strategy supported when a processor is set to
> use "On primary Node" is Timer Driven. There should be a second option to
> allow cron driven On primary Node scheduling strategy. This would allow
> users to more control over when a given primary node only processor runs.
> This would prevent these processors from running when configuration changes
> or instance restarts occur.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
