-
Notifications
You must be signed in to change notification settings - Fork 135
MySQL-kafka: wrong value for data type timestamp #957
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
测试:
timedatectl set-timezone UTC dest dest timedatectl set-timezone Europe/London src mysql timedatectl set-timezone Europe/Monaco dest mysql timedatectl set-timezone America/Los_Angeles # 开启目标端general log
set global general_log = ON;
set global general_log_file = '/tmp/general.log';
create table timestamp_columns( id int(11) not null primary key, c_timestamp timestamp)ENGINE=InnoDB DEFAULT CHARSET=utf8;
insert into timestamp_columns values (0,'1970-01-01 08:00:01');
insert into timestamp_columns values (1,'2037-01-19 11:14:07');
insert into timestamp_columns values (2,'2015-08-12 14:57:05');
insert into timestamp_columns values (3,now());
insert into timestamp_columns values (4,CURRENT_TIMESTAMP);
insert into timestamp_columns values (5,NULL);
insert into timestamp_columns values (10,'1970-01-01 08:00:01');
insert into timestamp_columns values (11,'2037-01-19 11:14:07');
insert into timestamp_columns values (12,'2015-08-12 14:57:05');
insert into timestamp_columns values (13,now());
insert into timestamp_columns values (14,CURRENT_TIMESTAMP);
insert into timestamp_columns values (15,NULL);
|
MySQL-MySQL :将源端用固定的time_zone 读取,目标端也用同一个time_zone写入 MySQL-Kafka将源端用固定的utc -0 的time_zone 读取 默认使用utc时区读写,考虑增加一个配置来决定读写时区 |
读取TIMESTAMP使用默认使用MySQL server的时区
|
MySQL 行为
|
fixed
|
Description
MySQL-kafka: wrong value for data type timestamp
Steps to reproduce the issue
shell> date 2022年 04月 20日 星期三 13:27:43 CST

5. check src MySQL binlogDescribe the results you expected
Output of
./dtle version
:**The text was updated successfully, but these errors were encountered: