[jira] [Commented] (NIFI-5030) ControlRate stops allowing FlowFiles through from same connection once limit for any 'group' is reached

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

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

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

GitHub user markap14 opened a pull request:

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

    NIFI-5030: If ControlRate encounters a FlowFile that cannot be transf…

    …erred, it should continue processing other FlowFiles that have different group attribute values
    
    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:
    - [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
         in the commit message?
    
    - [ ] 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.
    
    - [ ] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    - [ ] Is your initial contribution a single, squashed commit?
    
    ### For code changes:
    - [ ] 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?
    - [ ] 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/markap14/nifi NIFI-5030

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

    https://github.com/apache/nifi/pull/2593.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 #2593
    
----
commit 452e9493784cfc8fa08fe7f7b6f917e18e68ec2a
Author: Mark Payne <ma...@...>
Date:   2018-03-28T20:06:12Z

    NIFI-5030: If ControlRate encounters a FlowFile that cannot be transferred, it should continue processing other FlowFiles that have different group attribute values

----


> ControlRate stops allowing FlowFiles through from same connection once limit for any 'group' is reached
> -------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-5030
>                 URL: https://issues.apache.org/jira/browse/NIFI-5030
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>
> If we have FlowFiles in a single connection that feed into ControlRate, and we use the "Grouping Attribute" property, then whenever the processor encounters one FlowFile that should not continue on, subsequent FlowFiles in the queue will also not be transferred on either, even if they are of a different group.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)