That is a bit more tricky, but you could maybe handle the exception and build a custom failure message that routes into the aggregator, that then with the aggregation strategy builds a failed group and trigger its completion, that then is discarded afterwards.
There is also aggregate controller you can use http://static.javadoc.io/org.apache.camel/camel-core/2.18.0/org/apache/camel/processor/aggregate/AggregateController.html However we may want to add an option to force discard a group. I logged a ticket https://issues.apache.org/jira/browse/CAMEL-10533 On Fri, Nov 25, 2016 at 11:49 AM, morten <morten.skou.niel...@gmail.com> wrote: > I have a scenario where i am parsing a large csv file that contains a lot of > orderrows. I process each orderrow individually in different steps and then > use an aggregator to collect all orderows for a given order. The problem is > that during the processing an exception can occur which will move the > message to a deadletter queue. If this happen i have to discard the rows > that have already been aggregated. Question: > how do i signal to the aggregator that the aggregate must be dropped when > the failed message never passes to the aggregator? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Drop-aggregate-tp5790592.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
