You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/31 18:36:51 UTC

[jira] (NIFI-3422) Run Once Scheduling

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

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

GitHub user NazIrizarry opened a pull request:

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

    NIFI-3422 Run Once Scheduling

    Thank you for submitting a contribution to Apache NiFi.
    
    In order to streamline the review of the contribution we ask you
    to ensure the following steps have been taken:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [x] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
    - [x] Have you written or updated unit tests to verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
    - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
    - [ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [x] Have you ensured that format looks appropriate for the output in which it is rendered?
    
    ### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.


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

    $ git pull https://github.com/NazIrizarry/nifi NIFI-3422

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

    https://github.com/apache/nifi/pull/1458.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 #1458
    
----
commit 9c298395900e1840752fed7e7af191fbab497a45
Author: Naz Irizarry <na...@mitre.org>
Date:   2017-01-31T18:33:32Z

    - NIFI-3422 - Initial run once scheduling feature

----


> Run Once Scheduling
> -------------------
>
>                 Key: NIFI-3422
>                 URL: https://issues.apache.org/jira/browse/NIFI-3422
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core Framework, Core UI
>    Affects Versions: 1.2.0
>            Reporter: Nazario
>            Priority: Minor
>              Labels: features
>             Fix For: 1.2.0
>
>
> A run once scheduling option allows a Processor to run once and then automatically stop.  This is convenient when developing and debugging flows,  or when building "visual scripts" for ad-hoc process integration or iterative analytics. Individual processors set to `Run once' can be selected on the canvas with a shift-click.  Then clicking `Start' on the Operate Palette will start those processors which will run once and stop.  Then one can modify processing parameters and repeat.  Interactive analytics in particular benefit from this scheduling mode as they often require human review of results at the end of a flow followed by adjustment of flow parameters before running the next analytic flow.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)