You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2018/02/27 12:02:00 UTC
[jira] [Comment Edited] (CAMEL-10474) Aggregator - Allow
aggregate/preAggregate to force complete group
[ https://issues.apache.org/jira/browse/CAMEL-10474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378318#comment-16378318 ]
Claus Ibsen edited comment on CAMEL-10474 at 2/27/18 12:01 PM:
---------------------------------------------------------------
You can now set a exchange property with boolean true on the returned exchange from the aggregation repository
Exchange.AGGREGATION_COMPLETE_ALL_GROUPS
See the unit test for an example:
AggregateForceCompletionHeaderInAggregationStrategyTest
was (Author: davsclaus):
You can now set a header with boolean true on the returned exchange from the aggregation repository
Exchange.AGGREGATION_COMPLETE_ALL_GROUPS
See the unit test for an example:
AggregateForceCompletionHeaderInAggregationStrategyTest
> Aggregator - Allow aggregate/preAggregate to force complete group
> -----------------------------------------------------------------
>
> Key: CAMEL-10474
> URL: https://issues.apache.org/jira/browse/CAMEL-10474
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.21.0
>
>
> We should add support for end users to specify a special header in the returned message that will force the group to be complete, such as
> Exchange.AGGREGATE_FORCE_COMPLETE, true
> This can help the use case as described here
> http://stackoverflow.com/questions/40546189/aggregate-only-consecutive-exchanges-with-same-correlation-key
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)