[ https://issues.apache.org/jira/browse/NIFI-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589612#comment-15589612 ]
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_r84145273 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/WEB-INF/partials/canvas/processor-configuration.jsp --- @@ -108,6 +108,18 @@ </div> <div class="clear"></div> </div> + <div class="setting"> --- End diff -- The Scheduling Strategy and the Run Schedule should probably remain closer together. Can you shift the Execution Node setting below the Concurrent Tasks and Run Schedule. > 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)