-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Looks like special caracters are getting corupted #2151
Comments
please dump the schema for the table in question. jdbc options aren't important here. |
@osheroff Thank you for the response. I added the Table definition, The Value of the DB Filed looks fine if I do a select. |
what version of mysql? |
5.7.37-enterprise-commercial-advanced-log |
ok, I can't reproduce this trivially. what's the output of this?
and this?
|
@osheroff, thank you. I think I see now what the Problem is:
Will let maxwell read the schema again and that should be it I think |
yeah. I wish i knew why / how it ended up this way, but you're right about the fix |
I am running a maxwell to get data from a mysql bin log and write it to a RabbitMq with a docker container
Image: zendesk/maxwell:v1.41.2
For instance I update the filed with a mysql client like this:
update auftrag set Gewerk = '21 Lüftung' where nr = 2024170075;
Source DB settings (from the mysql client):
the Log entry from Maxwell is as followed:
2025-01-16 11:59:39 DEBUG RabbitmqProducer - -> routing key:db.auftrag, partition:{"database":"db","table":"auftrag","type":"update","ts":1737028779,"xid":153331256,"commit":true,"data":{"Nr":2024170075","GewerkNr":"21","Gewerk":"21 Lüftung"}}
it looks like the utf-8 strings are getting curruped for some reason (this looks like ascii in the log) and this is also what gets pushed to RabbitMQ
I tried to set the jdbc options with the enviroment variable
REPLICATION_JDBC_OPTIONS:useUnicode=true&characterEncoding=UTF-8
but it had no effectTable Definition:
My next try will be to set the
config.properties
and add the JDBC options from thereAny Idea what else I can set to resolve this?
The text was updated successfully, but these errors were encountered: