[ 
https://issues.apache.org/jira/browse/NIFI-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15589614#comment-15589614
 ] 

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_r84139832
  
    --- Diff: 
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/js/nf/nf-processor-details.js
 ---
    @@ -166,15 +167,20 @@ nf.ProcessorDetails = (function () {
     
                         // make the scheduling strategy human readable
                         var schedulingStrategy = 
details.config['schedulingStrategy'];
    +                    var executionNode = details.config['executionNode'];
                         if (schedulingStrategy === 'EVENT_DRIVEN') {
                             showRunSchedule = false;
                             schedulingStrategy = 'Event driven';
                         } else if (schedulingStrategy === 'CRON_DRIVEN') {
                             schedulingStrategy = 'CRON driven';
                         } else if (schedulingStrategy === 'TIMER_DRIVEN') {
                             schedulingStrategy = "Timer driven";
    -                    } else {
    -                        schedulingStrategy = "On primary node";
    +                    } else if (schedulingStrategy === 'PRIMARY_NODE_ONLY') 
{
    --- End diff --
    
    Again, I don't think we want to infer the configuration here. We should 
continuing showing 'On primary node' if the component is configured with it.


> 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)

Reply via email to