Skip to content

Fix Kafka SMT kamelets for CAMEL-23584 header rename#2875

Merged
oscerd merged 1 commit into
apache:mainfrom
mcarlett:fix/kafka-header-rename-camel-23584
Jun 24, 2026
Merged

Fix Kafka SMT kamelets for CAMEL-23584 header rename#2875
oscerd merged 1 commit into
apache:mainfrom
mcarlett:fix/kafka-header-rename-camel-23584

Conversation

@mcarlett

@mcarlett mcarlett commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Summary

CAMEL-23584 renamed all camel-kafka Exchange header constants from kafka.* to CamelKafka* prefix, but two kamelet YAML definitions were not updated, causing silent failures:

  • topic-name-matches-filter-action: ${header[kafka.TOPIC]} is always null → filter drops all messages
  • timestamp-router-action: timestampHeaderName defaults to kafka.TIMESTAMP (null) → timestamp never read → override topic never set

Changes

  • topic-name-matches-filter-action.kamelet.yaml: ${header[kafka.TOPIC]}${header[CamelKafkaTopic]}
  • timestamp-router-action.kamelet.yaml: timestampHeaderName default kafka.TIMESTAMPCamelKafkaTimestamp

Both in kamelets/ and library/camel-kamelets/src/main/resources/kamelets/.

CAMEL-23584 renamed all camel-kafka Exchange header constants from
kafka.* to CamelKafka* prefix. Two kamelet YAML definitions still
used the old names, causing silent failures:

- topic-name-matches-filter-action: ${header[kafka.TOPIC]} → ${header[CamelKafkaTopic]}
- timestamp-router-action: timestampHeaderName default kafka.TIMESTAMP → CamelKafkaTimestamp
@oscerd oscerd merged commit 49d30bc into apache:main Jun 24, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants