[
https://issues.apache.org/jira/browse/CAMEL-14362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafał Gała updated CAMEL-14362:
-------------------------------
Summary: Set metadata for each aggregated kafka message separately (was:
Set metadata for each eggregated kafka message separately)
> Set metadata for each aggregated kafka message separately
> ---------------------------------------------------------
>
> Key: CAMEL-14362
> URL: https://issues.apache.org/jira/browse/CAMEL-14362
> Project: Camel
> Issue Type: New Feature
> Components: camel-kafka
> Reporter: Rafał Gała
> Priority: Minor
>
> This feature introduces setting metadata on aggregated exchange individually.
> Currently, when many aggregated messages are sent, metadata is set only on
> aggregating exchange as a list. It is then difficult to match metadata from
> the list with aggregated exchange it refers to, because the order in the list
> does not have to be the same as the order of aggregated exchanges. When using
> asynchronous kafka producing, callbacks that set metadata can be called in
> different order than the messages were produced to kafka.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
