You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2016/04/15 02:13:25 UTC

[jira] [Commented] (NIFI-1775) Add time-based merge capability to MergeContent processor

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

Aldrin Piri commented on NIFI-1775:
-----------------------------------

Hey Randy,

There is a "Max Bin Age" property for MergeContent, does that solve the case you are trying to address?  If not, could you please provide some additional information or examples so we can establish a strategy to address it?

Thanks!

> Add time-based merge capability to MergeContent processor
> ---------------------------------------------------------
>
>                 Key: NIFI-1775
>                 URL: https://issues.apache.org/jira/browse/NIFI-1775
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Randy Gelhausen
>
> MergeContent collects a certain size of data or number of events prior to emitting a merged flowfile. This works well for rapid ingestion, as usually downstream consumers see merged FlowFiles with acceptable latency.
> However, some ingest rates are spiky, or infrequent, greatly increasing the latency a downstream consumer sees. Adding a time-based merge window would be very useful.



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