[
https://issues.apache.org/jira/browse/CAMEL-14414?focusedWorklogId=383953&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-383953
]
ASF GitHub Bot logged work on CAMEL-14414:
------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Feb/20 08:29
Start Date: 08/Feb/20 08:29
Worklog Time Spent: 10m
Work Description: davsclaus commented on pull request #3554: CAMEL-14414:
back port to 3.0.x for aggregation group completion setting and removal is …
URL: https://github.com/apache/camel/pull/3554
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 383953)
Time Spent: 1h 20m (was: 1h 10m)
> Aggregation completion has inconsistent property/header handling
> ----------------------------------------------------------------
>
> Key: CAMEL-14414
> URL: https://issues.apache.org/jira/browse/CAMEL-14414
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.24.3, 3.x
> Reporter: Gianandrea Rigoni
> Priority: Major
> Fix For: 3.1.0, 3.0.2, 2.25.1
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> following headers or properties are handled in an inconsistent way
> sometimes setted as prop then removed as headers or viceversa
> documentation in describing how to set them is also slightly inconsistent
> affected flags are (I am on purpose avoiding naming them header or property)
> AGGREGATION_COMPLETE_CURRENT_GROUP
> AGGREGATION_COMPLETE_ALL_GROUPS
> AGGREGATION_COMPLETE_ALL_GROUPS_INCLUSIVE
> also chaining aggregations is not working when using
> AGGREGATION_COMPLETE_CURRENT_GROUP
> AGGREGATION_COMPLETE_ALL_GROUPS
> because setting is done on prop and removal is done on header level
> I have created a PR proposing a change
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
