[
https://issues.apache.org/activemq/browse/CAMEL-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52126#action_52126
]
Claus Ibsen commented on CAMEL-1686:
------------------------------------
[17:14] <davsclaus> well the issue is when you use completion predicate it
waits until either timeout or a batch size limit was hit
[17:15] <davsclaus> so the problem is when you use a completion predicate
[17:15] <davsclaus> it cannot check it on-the-fly
[17:15] <jstrachan> ah :)
[17:15] <jstrachan> so we need it to wait unil "either timeout or a batch size
limit was hit" or completion predicate true?
[17:18] <davsclaus> yeah the latter is missing
[17:18] <davsclaus> that is because that one is computed when the aggregation
occurs (and it starts by the first 2)
[17:19] <davsclaus> what it does is just batching up,
[17:19] <davsclaus> so we should let it aggregate on-the-fly and let it be
able to trigger completion if the completion predicate = true
[17:19] <jstrachan> agreed
> Aggregator - Completion Predicate being evaluated on-the-fly
> ------------------------------------------------------------
>
> Key: CAMEL-1686
> URL: https://issues.apache.org/activemq/browse/CAMEL-1686
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.6.2, 2.0.0
> Reporter: Claus Ibsen
> Fix For: 2.1.0
>
>
> When using the completion predicate with the aggregator its not evaluated
> on-the-fly. So the completion is dependent on timeout or batch size before
> its evaluated.
> We should let Camel be able to aggregate on-the-fly so the completion
> predicate also can trigger a send from the aggregator.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
