Chinese garbled(中文乱码),The Chinese description of the field in the mysql database is garbled,

[fanhl]

[SakuraAxy]

I also encountered this problem and tried adding source.optons.encoding: utf-8
But it doesn't work and problems still happen

[Light310]

Looks like cyrillic also broken

[dexter-mh-lee]

We recently updated init.sql to take in UTF8, but it doesn't convert existing ones. In the meantime can you try running

ALTER TABLE metadata_aspect_v2 CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;

In the MySQL db?

[itc180016]

I just updated Datahub to V0.8.11, and using PostgreSQL. The same problem was encountered. What should I do?

[NightCat000]

I also need to resolve the situation which don't support the chinese charset.

[1ambda]

Hi, after upgrading to 0.8.11 w/ Postgres, encountered the same problem.

• dataset name, description, user name, ...

Datahub encoding is UTF-8.

SELECT pg_encoding_to_char(encoding) FROM pg_database WHERE datname = 'datahub_prod';

> UTF-8

And created database using `ko_KR.UTF-8'.

CREATE DATABASE datahub_prod OWNER xxx ENCODING 'UTF8' LC_COLLATE = 'C' LC_CTYPE = 'ko_KR.UTF-8' TEMPLATE template0;

[dexter-mh-lee]

Just to clarify. Do you see it correctly added to the MySQL/Postgres DB, but see bad decoding in the UI? or is it incorrectly ingested in the first place? @itc180016 @NightCat000 @1ambda

[dexter-mh-lee]

Hi everyone. We identified the issue. We will fix it asap and cut a release

[1ambda]

Hi, @dexter-mh-lee

In my case, We can see the text in DB and ES clearly in the original encoding, but Seems UI or API doesn't handle them correctly. and It's first time. It happened after upgrading to 0.8.11.

[NightCat000]

I already have solved the problem,if you want to know how to solve,please clicking folowing:
https://blog.nowcoder.net/n/df53c7e3699d4828bcc1084f7e11bd36

[Echelon77]

I already have solved the problem,if you want to know how to solve,please clicking folowing:
https://blog.nowcoder.net/n/df53c7e3699d4828bcc1084f7e11bd36

It doesn't work for me. Maybe the reason is that the header of frontend reponse not set utf8, it responsed this: 'text/plain; charset=ISO-8859-1'

[NightCat000]

I already have solved the problem,if you want to know how to solve,please clicking folowing:
https://blog.nowcoder.net/n/df53c7e3699d4828bcc1084f7e11bd36

It doesn't work for me. Maybe the reason is that the header of frontend reponse not set utf8, it responsed this: 'text/plain; charset=ISO-8859-1'

I don’t know clearly why you are ,maybe you need to build new datahub after fixed it 。

[Echelon77]

I already have solved the problem,if you want to know how to solve,please clicking folowing:
https://blog.nowcoder.net/n/df53c7e3699d4828bcc1084f7e11bd36

It doesn't work for me. Maybe the reason is that the header of frontend reponse not set utf8, it responsed this: 'text/plain; charset=ISO-8859-1'

I don’t know clearly why you are ,maybe you need to build new datahub after fixed it 。

Yes，I pull the latest code and rebuild a new docker image, now it's solved.

[shirshanka]

This has been fixed via #3168 and is now available on head as @Echelon77 mentioned.

We will cut a release (0.8.12) that contains this fix by end of this week.
Please re-open if that doesn't resolve it.

[1ambda]

It's fixed after upgrading to 0.8.12 :) Thanks.