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

2016-04-14 Thread Randy Gelhausen (JIRA)

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

Randy Gelhausen commented on NIFI-1775:
---

This works! 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)


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

2016-04-14 Thread Aldrin Piri (JIRA)

[ 
https://issues.apache.org/jira/browse/NIFI-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)