[
https://issues.apache.org/jira/browse/NIFI-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589616#comment-15589616
]
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_r84136907
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/canvas/nf-processor-configuration.js
---
@@ -632,11 +633,22 @@ nf.ProcessorConfiguration = (function () {
value: processor.config['bulletinLevel']
});
+ // If the scheduling strategy is PRIMARY_NODE_ONLY
(deprecated),
+ // then set the execution node to PRIMARY and the
scheduling
+ // strategy to TIMER. These new values will be saved
when/if
+ // the dialog is applied.
+ var schedulingStrategy =
processor.config['schedulingStrategy'];
+ var executionNode = processor.config['executionNode'];
+ if (schedulingStrategy === 'PRIMARY_NODE_ONLY') {
--- End diff --
This appears to be rendering the inferred configuration based on the
currently (now deprecated) option. I think we should be rendering what is
actually configured. If the option is now deprecated we should mark the item as
disabled to prevent it from being selected again. But I do not believe we
should be rendering something that is not actually configured.
> 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)
