Source MySQL VARCHAR/CHAR columns with utf8mb3_bin collation are encoded as BASE64

Hi there,
We are connecting MySQL as source connector.
In our MySQL db (type=VARCHAR, charset=utf8mb3, collation=utf8mb3_bin), then we found this column will be by default encoded as BASE64. But the expectation is still outputting string value.

it is related to usage of field.isBinary() flag in source connector, which either source mysql have wrong interpretation or field.isBinary is returning wrong value as designed because the collation is just deciding how values are compared. the column is still a string type.

To repro, just create this table in mysql db:
CREATE TABLE charset_test (
char1 VARCHAR(100) COLLATE utf8mb4_bin,
char2 VARCHAR(100) COLLATE utf8mb3_bin,
char3 VARCHAR(100) COLLATE utf8mb4_general_ci);
INSERT INTO charset_test VALUES (“utf8mb4_bin”, “utf8mb3_bin”, “utf8mb4_general_ci”);

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team