Repository navigation
Use application headers in Kafka router integration tests - #3113
Merged
oscerd merged 1 commit intoOct 23, 2026
Merged
Conversation
oscerd
approved these changes
Oct 21, 2026
davsclaus
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The HTTP-to-Kafka router integration fixture still uses the legacy Camel Kafka names
kafka.TOPICandkafka.TIMESTAMPas application headers and explicitly configures TimestampRouter to read them.Rename those HTTP query parameters to
topicandtimestamp, keeping the router configuration in sync. TimestampRouter continues to write the currentCamelKafkaOverrideTopicheader. Using application header names at the HTTP boundary avoids confusion with Camel-internal headers, which transport header filters exclude.This is fixture cleanup following a review of the Camel 4.19–4.22.1 header renames. Salesforce is already corrected on main. The corresponding 4.22.x cleanup and packaged Salesforce synchronization are in #3112.
Validation:
mvn verifypassed; 20 catalog unit tests passed.mvn verify -pl :camel-kamelets-itest -Denable.integration.tests -Dit.test=KafkaITpassed all 3 tests, including the HTTP-to-Kafka timestamp router.git diff --checkpassed.AI-generated by Codex on behalf of Federico Mariani.