[jira] [Work logged] (CAMEL-14414) Aggregation completion has inconsistent property/header handling

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-14414?focusedWorklogId=374064&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-374064 ]

ASF GitHub Bot logged work on CAMEL-14414:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Jan/20 14:20
            Start Date: 18/Jan/20 14:20
    Worklog Time Spent: 10m 
      Work Description: grigoni commented on pull request #3494: CAMEL-14414: for aggregation group completion setting and removal is …
URL: https://github.com/apache/camel/pull/3494
 
 
   …handled through methods to enforce code cohesion and avoid repetitions. fixed issue for CURRENT_GROUP and ALL_GROUPS flag removal. adapted tests and documentation
 
----------------------------------------------------------------
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:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 374064)
    Remaining Estimate: 0h
            Time Spent: 10m

> Aggregation completion has inconsistent property/header handling
> ----------------------------------------------------------------
>
>                 Key: CAMEL-14414
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14414
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.24.3, 3.x
>            Reporter:  Gianandrea Rigoni
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> following headers or properties are handled in an inconsistent way
> sometimes stetted 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)