[
https://issues.apache.org/jira/browse/NIFI-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314046#comment-15314046
]
Oleg Zhurakousky commented on NIFI-1926:
----------------------------------------
Sure [~markap14]. So recently couple of use cases have been discussed on the
list, so I'll list some that I remember:
1. Correlating the input coming from multiple upstream connections
2. Configurable aggregation strategies (I may not want to merge, rather output
a collection of FF)
3. Time-based batches (e.g., release what you've accumulated for a particular
correlation ID every 5 sec)
I'll list more as I remember.
> Create a general purpose Aggregating processor
> ----------------------------------------------
>
> Key: NIFI-1926
> URL: https://issues.apache.org/jira/browse/NIFI-1926
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Oleg Zhurakousky
> Assignee: Oleg Zhurakousky
>
> Based on multiple question on mailing list it appears that we need to have a
> general purpose processor to aggregate data (FlowFiles or content of
> FlowFiles etc). Basically provide an implementation of this
> http://www.enterpriseintegrationpatterns.com/patterns/messaging/Aggregator.html
> Keep in mind that while MergeContent processor could be looked at as one of
> the variation of aggregation, the pattern and the problem has much more
> moving parts that need to be addressed (release, correlation, and aggregation
> strategies). So the new processor should be flexible enough to handle variety
> of aggregation use cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
