I narrowed down the problem to this: 1) Camel correlation selects records based on some key field. 2) Camel aggregation retrieves existing record from repository based on the key field. 3) Camel checks if aggregation is completed by consulting the completion predicate. 4) New correlation key comes into play.
It looks like there is no way to tell Camel to evaluate the completion predicate when the new correlation key enters the scene? In this scenario Camel is checking the completion predicate at the same time the new record enters the scene, so returning TRUE from completion predicate says 'the new record is the last one from its batch', which is not right. Would anyone have any ideas on how to tackle this, short of implementing some kind of read-behind scenario? Thanks, Mark -- View this message in context: http://camel.465427.n5.nabble.com/problems-with-Camel-aggregation-pattern-tp4669621p4669795.html Sent from the Camel - Users mailing list archive at Nabble.com.
