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

ASF GitHub Bot commented on NIFI-401:
-------------------------------------

GitHub user beugley opened a pull request:

    https://github.com/apache/nifi/pull/512

    NIFI-401

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/beugley/nifi NIFI-401

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/512.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #512
    
----
commit 011b5e724648d3f72746b18e17e79be0ebee200d
Author: Brian Eugley <[email protected]>
Date:   2016-06-09T15:32:15Z

    NIFI-401

----


> 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