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

Sending messages to IBM MQ with a different encode than UTF-8 #42

Open
brenofr opened this issue Jul 20, 2021 · 2 comments
Open

Sending messages to IBM MQ with a different encode than UTF-8 #42

brenofr opened this issue Jul 20, 2021 · 2 comments

Comments

@brenofr
Copy link

brenofr commented Jul 20, 2021

Hello!

I have 2 points here:

  1. I'd like to know if there a way to send a message to a IBM MQ queue using a different encode (like "IBM500").
    In my need, I noticed that there's data loss caused by the differences between a content that is received as EBCDIC (IBM500) and the default value used by IBM MQ Sink connector is UTF-8.

  2. I'd like to know if is it possible to input a custom source code into the connector to force the ccsid.

PS.: I can't change the CCSID of que Queue Manager.

@jhughes24816
Copy link
Contributor

jhughes24816 commented May 5, 2023

Hi @brenofr sorry it has taken so long to respond to this.

  1. Some details of message format options can be found in this section of the README which give some details about message formatting however is no reference to supporting alternative encodings.
  2. At the moment, this is not possible as the encoding is fixed to UTF-8. It might be possible to expose this as part of the connector config.

I will raise it with the development team.

@theodore-evans
Copy link

Hi @brenofr, @jhughes24816 fyi,

I have just opened a PR on the IBM MQ source connector repo to add support for configuring the connector with a non-default CCSID: ibm-messaging/kafka-connect-mq-source#125

Provided there are no issues with this going through, the same approach could be implemented for the sink connector.

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

No branches or pull requests

3 participants