[
https://issues.apache.org/jira/browse/NIFI-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15591892#comment-15591892
]
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_r84288620
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/WEB-INF/partials/processor-details.jsp
---
@@ -103,6 +103,18 @@
<div class="clear"></div>
</div>
<div class="setting">
+ <div id="details-execution-node-container"
class="execution-node-setting">
--- End diff --
No worries. I don't think there are a lot of problems with the code. I
think what was provided is quite good and really close. Most comments are
mostly based on the same premise of retaining the existing configuration until
a user has explicitly configured a Processor using the new options. I just
tried to mark each spot where we should consider that.
Either way, I am happy to continue working with you on this PR or I would
be happy to pick up at this point if you'd prefer.
Thanks again!
> 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)
