[
https://issues.apache.org/jira/browse/CAMEL-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041762#comment-14041762
]
Antoine DESSAIGNE commented on CAMEL-7015:
------------------------------------------
At first I though of adding an option telling whether or not the timeout is for
the first message received in this correlation group or for the last message.
But then I though, why not provide both timeouts ? You might want to 5 seconds
after the last exchange received but not more than 60 seconds after the first
message. That way, if you have an exchange every 4 seconds, you'll aggregate
after one minute an not any longer.
Thus I named this parameter {{maxCompletionTimeout}} because I didn't wanted to
rename the {{completionTimeout}} parameter.
I'm not saying that it's the right way, or maybe it's not properly named. Don't
hesitate to ask if you want more insights about this patch.
> Allow timeout on the first Exchange for aggregator
> --------------------------------------------------
>
> Key: CAMEL-7015
> URL: https://issues.apache.org/jira/browse/CAMEL-7015
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, eip
> Reporter: ChrisS
> Assignee: Willem Jiang
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> It would be nice to have a possibility of a timeout starting from the first
> Exchange for messages having the same correlationExpression when using
> Aggregation.
> This scenario is currently not supported because "Its a bit tougher to
> implement as it would require an improvement to TimeoutMap to support that as
> well."
> The full scenario is described in this thread:
> http://camel.465427.n5.nabble.com/A-simple-Aggregator-use-case-td5743633.html#a5743634
--
This message was sent by Atlassian JIRA
(v6.2#6252)
