[jira] [Commented] (NIFI-4155) Expand EnforceOrder capability to cluster

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user ijokarumawak opened a pull request:

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

    NIFI-4155: Expand EnforceOrder capability to cluster

    - Added 'Ordering Scope' to specify how it should manage state, to choose from local and cluster.
    - Avoid unnecessary status update if it does not make any progress, only update it when order proceeds.
    - If updating state fails, due to it is already updated by other nodes, rollback the session to process the same FlowFiles again.
    
    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?
    - [ ] 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?
    - [x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?
    
    ### For documentation related changes:
    - [ ] 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/ijokarumawak/nifi nifi-4155

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

    https://github.com/apache/nifi/pull/1984.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 #1984
    
----
commit 11fa5ff13b5fcc5b8f5b1de577b8a061cc4ca174
Author: Koji Kawamura <ij...@apache.org>
Date:   2017-07-06T11:53:23Z

    NIFI-4155: Expand EnforceOrder capability to cluster
    
    - Added 'Ordering Scope' to specify how it should manage state, to choose from local and cluster.
    - Avoid unnecessary status update if it does not make any progress, only update it when order proceeds.
    - If updating state fails, due to it is already updated by other nodes, rollback the session to process the same FlowFiles again.

----


> Expand EnforceOrder capability to cluster
> -----------------------------------------
>
>                 Key: NIFI-4155
>                 URL: https://issues.apache.org/jira/browse/NIFI-4155
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Koji Kawamura
>            Assignee: Koji Kawamura
>
> Currently, EnforceOrder is able to enforce FlowFile ordering within a NiFi node, and it uses local managed state to track progress.
> If it is configurable which state management to use from Local and Cluster, EnforceOrder would be also able to enforce ordering across cluster with cluster scope state management. It would be useful for some use-cases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)