[
https://issues.apache.org/activemq/browse/CAMEL-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45689#action_45689
]
Gert Vanthienen commented on CAMEL-876:
---------------------------------------
http://svn.eu.apache.org/viewvc?view=rev&revision=695358 shows what I meant --
like a CountDownLatch, but which allows to increment() the count as more
exchanges are being sent.
There now is one more step left: for aggregating the exchanges, we still need
the entire list of exchanges. We can aggregate them on the fly as the
exchanges get answered, but this no longer guarantees the order of aggregation.
Unless someone objects, I'm going to move the {{streaming}} flag up from the
{{Splitter}} to the {{MulticastProcessor}}, once again giving people the choice
to use the new approach, but warning them about the out-of-order behavior in
the the aggregator.
> splitter() should support batch for processing large files
> ----------------------------------------------------------
>
> Key: CAMEL-876
> URL: https://issues.apache.org/activemq/browse/CAMEL-876
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.4.0
> Reporter: Claus Ibsen
> Assignee: Gert Vanthienen
> Fix For: 1.5.0
>
>
> See nabble:
> http://www.nabble.com/Splitter-for-big-files-td19272583s22882.html
> Somekind of batch(size) parameter to the splitter() DSL so we can process the
> exchanges in batches instead of all in one go.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
