[ https://issues.apache.org/jira/browse/NIFI-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589615#comment-15589615 ]
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_r84133750 --- Diff: nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/css/processor-configuration.css --- @@ -110,6 +110,12 @@ div.processor-enabled-container { line-height: 18px; } +#execution-node-combo { --- End diff -- With the updated UI in 1.0.0 I don't think this style is necessary anymore. Specifically the width and height are not consistent with the other combos in the scheduling tab. > 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)