-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Bug] [Zeta] Synchronize data from MySQL to Hive Chinese field garbled code #5244
Comments
Do you get garbled characters when you insert into xx in hive? |
I will try to fix it! |
Can you provide your hive ddl @chuansenwang |
This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs. |
This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future. |
Search before asking
What happened
I deployed a seatunnel cluster using a container and attempted to synchronize data from the MySQL database to the Hive warehouse. However, I found that the Hive Chinese fields were garbled during the query
MySQL database query display
123 张三 10
124 李四 10
Hive database query display
123,??,10
124,??,10
The data I insert through commands on the console will not be garbled
INSERT INTO student VALUES (1234,"哈哈2",12);
Hive database query display
123,??,10
124,??,10
1234,"哈哈2",12
SeaTunnel Version
seatunnel 2.3.2
mysql 5.7
hive 3.1.3
hadoop 3.3.5
jdk 1.8
SeaTunnel Config
Running Command
Error Exception
Zeta or Flink or Spark Version
No response
Java or Scala Version
jdk 1.8
Screenshots
创建Hive语句
CREATE TABLE IF NOT EXISTS student(
id INT COMMENT 'ID',
name STRING COMMENT '名字',
age INT COMMENT '年龄'
)
ROW FORMAT DELIMITED
FIELDS TERMINATED BY ','
LINES TERMINATED BY '\n';
MySQL 数据库语句:
CREATE TABLE
Student
(id
bigint(20) NOT NULL,name
varchar(255) DEFAULT NULL,age
int(2) DEFAULT NULL,sex
tinyint(1) DEFAULT NULL,address
varchar(255) DEFAULT NULL,PRIMARY KEY (
id
)) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: