You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joe Skora (JIRA)" <ji...@apache.org> on 2016/12/06 18:22:58 UTC
[jira] [Updated] (NIFI-2861) ControlRate should accept more than
one flow file per execution
[ https://issues.apache.org/jira/browse/NIFI-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Skora updated NIFI-2861:
----------------------------
Status: Patch Available (was: Open)
Pull requests entered Oct 13, 2016, [PR#1127|https://github.com/apache/nifi/pull/1127] for 1.x and [PR#1128|https://github.com/apache/nifi/pull/1128] for 0.x.
Updated Oct 18, 2016 for review comments.
> ControlRate should accept more than one flow file per execution
> ---------------------------------------------------------------
>
> Key: NIFI-2861
> URL: https://issues.apache.org/jira/browse/NIFI-2861
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.7.0, 1.0.0
> Reporter: Joe Skora
> Assignee: Joe Skora
>
> The {{ControlRate}} processor implements a {{FlowFileFilter}} that returns the {{FlowFileFilter.ACCEPT_AND_TERMINATE}} result if the {{FlowFile}} fits with the rate limit, affectively limiting it to one {{FlowFile}} per {{ConrolRate.onTrigger()}} invocation. This is a significant bottleneck when processing very large quantities of small files making it unlikely to hit the rate limits.
> It should allow multiple files, perhaps with a configurable maximum, per {{ControlRate.onTrigger()}} invocation by issuing the {{FlowFileFilter.ACCEPT_AND_CONTINUE}} result until the limits are reached. In a preliminary test this eliminated the bottleneck.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)