[
https://issues.apache.org/jira/browse/NIFI-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595721#comment-15595721
]
ASF GitHub Bot commented on NIFI-401:
-------------------------------------
Github user beugley commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1117#discussion_r84516844
--- 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 --
yep, as you noted my goal was to accept processors with older
configurations, and then update to a newer configuration when the user changed
the processor in any form. At the moment, I'm very busy with other tasks, so
don't have time to work on this now, and won't in the near future. If you want
to pick this up, go ahead, I won't be offended in any way. Thanks again for
reviewing it and considering the change!
Brian
> 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)
