[
https://issues.apache.org/jira/browse/NIFI-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589613#comment-15589613
]
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_r84142131
--- Diff:
nifi-api/src/main/java/org/apache/nifi/scheduling/SchedulingStrategy.java ---
@@ -56,6 +56,10 @@
*/
TIMER_DRIVEN(1, "0 sec"),
/**
+ * NOTE: This option has been deprecated with the addition of the
+ * execution-node combo box. It still exists for backward
compatibility
+ * with existing flows that still have this value for
schedulingStrategy.
+ **
--- End diff --
Probably should actually mark this option as deprecated using an annotation.
> 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)