You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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)
The text was updated successfully, but these errors were encountered: