[CAMEL-16472] kamelet: aggregation kamelet not wired properly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.9.0
• Fix Version/s: 3.10.0
• Component/s: camel-kamelet, camel-yaml-dsl
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Luca Burgazzoli
• Created: 08/Apr/21 17:17
• Updated: 14/Apr/21 09:05
• Resolved: 14/Apr/21 09:05

Description

Assuming we have a kamelet named aggregate that define an aggregation step, like:

- from: 
    uri: "kamelet:source"
    steps: 
      - aggregate: 
          correlation-expression: 
            simple: "${header.Kind}"
          strategy-ref: "myAggregatorStrategy"
          completion-size: "{{count}}"
          steps: 
            - to: "log:aggregate"
            - to: "kamelet:sink"

And a route using such kameelt:

- from: 
    uri: "timer:tick"
    steps: 
      - set-header: 
          name: "Kind"
          constant: "simple"
      - set-body: 
          simple: "${exchangeProperty.CamelTimerCounter}"
      - to: "kamelet:aggregate?count=5"
      - to: "log:info"

When this code is executed, the_ log:info_ endpoint will log each individual exchange produced by the timer but not the aggregated one which is instead logged by the log:aggregate endpoint (part of the aggregate kamelet).

This happen because the route engine does not wire the kamelet:sink endpoint of the aggregate kamemelt but the route output.

Issue Links

• is fixed by: CAMEL-16487 camel-request-reply - Component for request reply using in-memory queue
• is fixed by: CAMEL-16493 camel-kamelet - Kamelet EIP