Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MQ sink does not map headers from Kafka source #1321

Closed
davsclaus opened this issue Mar 1, 2023 · 3 comments · Fixed by #1323
Closed

MQ sink does not map headers from Kafka source #1321

davsclaus opened this issue Mar 1, 2023 · 3 comments · Fixed by #1323
Assignees
Milestone

Comments

@davsclaus
Copy link
Contributor

I have been told that an user have trouble with sourcing from Kafka and sinking to IBM MQ then headers are not mapped, and they want Kafka Key to be mapped as JMSCorrelationID as well.

I think they may have seen this example
https://github.com/apache/camel-kamelets/blob/main/kamelets/jms-ibm-mq-sink.kamelet.yaml

They are using Camel K and KameletBinding to setup the source and sink (no step in-between)

@davsclaus
Copy link
Contributor Author

There is a generic MQ example here. Maybe it can be used to test and see
https://github.com/apache/camel-k-examples/tree/main/generic-examples/ibm-mq

@oscerd oscerd self-assigned this Mar 1, 2023
@oscerd
Copy link
Contributor

oscerd commented Mar 1, 2023

I'll have a look

@oscerd
Copy link
Contributor

oscerd commented Mar 1, 2023

Using deserializeHeaders and setting it to true will work. This needs to be done also a kafka source not secured Kamelet

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 a pull request may close this issue.

2 participants