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

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

GitHub user pvillard31 opened a pull request:

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

    NIFI-2751 - Pull batch in round-robin manner - fix for / by 0

    

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

    $ git pull https://github.com/pvillard31/nifi NIFI-2751

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

    https://github.com/apache/nifi/pull/1211.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 #1211
    
----
commit 72e09eab333ee0a14936d77b76a5c5efca5a1395
Author: Pierre Villard <[email protected]>
Date:   2016-11-12T11:10:43Z

    NIFI-2751 - Pull batch in round-robin manner - fix for / by 0

----


> When a processor pulls a batch of FlowFiles, it keeps pulling from the same 
> inbound connection instead of round-robin'ing
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-2751
>                 URL: https://issues.apache.org/jira/browse/NIFI-2751
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Pierre Villard
>            Priority: Blocker
>              Labels: beginner, easyfix, framework, newbie
>             Fix For: 1.1.0
>
>
> When a Processor calls ProcessSession.get(int) or 
> ProcessSession.get(FlowFileFilter), the FlowFiles only come from the first 
> inbound connection, unless that connection is empty or doesn't have enough 
> FlowFiles to complete the get() call. It should instead round-robin between 
> the incoming connections, just as ProcessSession.get() does.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to