Timeout=0 is the very essence of what I'm trying to express, I'm not sure how I can be both "correct" and "making no sense" :-)
I'd have guessed this was a common use case and would be a useful feature. Consider a processor posting to a seda which consumes messages and posts them in batch to a variable speed sink, say a network resource. It's reasonable for some applications to want to avoid any pointless idle time if there are 10 messages available immediately that could be dealt with. If the network link is being slower than expected then by the time it next polls the seda, there may be 100 messages to pick. I think the problem is that completionSize specifies both a maximum and minimum size. Ideally I would specify a range (eg "wait for at least 5 messages; if more than 5 messages are already available, take them all, up to a limit of 100"). Is this something that would be difficult to plumb into the existing aggregator? — Sent from Mailbox On Mon, Oct 27, 2014 at 9:55 PM, akoufoudakis <akoufouda...@gmail.com> wrote: > And, of course, time out, set to 0, makes no sense... > -- > View this message in context: > http://camel.465427.n5.nabble.com/Aggregate-up-to-N-ASAP-tp5758134p5758140.html > Sent from the Camel - Users mailing list archive at Nabble.com.
