It seems that the completionSize attribute of the aggregator will "make up
the difference" if there are no more messages.
I'd like to be able to do something like:
<aggregate strategyRef="myAggregationStrategy"
completionSize="500">
<correlationExpression>
<constant>true</constant>
</correlationExpression>
<to id="out"
uri="sftp://some...@something.com/test/"; />
</aggregate>
Where, the from on this route is a queue that gets in 500+ messages at a
time and it puts them together in batches of 500. This works fine, if you
actually have 500 messages. However, if you have less than 500, it
duplicates messages to make it 500.
I tried to use a completionPredicate instead, but I suspect that I have to
do something that is a hybrid of a completionSize and a completionTimeout.
Or perhaps I am over thinking this?
Is there a way to do what I am trying to do in Camel (v2.11 FWIW)?
--
View this message in context:
http://camel.465427.n5.nabble.com/aggregator-dynamic-completion-size-tp5733048.html
Sent from the Camel - Users mailing list archive at Nabble.com.
