alibaba / alibaba/DataX

datax同步mysql到hive时区

Open
#1,189 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
17.4k
Forks
5.7k
PR merge metrics
No merged PRs in 30d

Description

mysql数据表
CREATE TABLE `asr_call_bak` (
`uui_call_id` varchar(50) NOT NULL COMMENT '通话ID',
`created_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间',
`updated_at` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP COMMENT '修改时间'
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
数据:
1 2021-03-02 17:54:25 2021-04-12 09:53:30

导入到hive 数据都是String类型的
1 2021-03-03 07:54:25.000 2021-04-12 22:53:30.000
时间差距 13个小时

我尝试改动了启动脚本 datax.py 添加了
![image](https://user-images.githubusercontent.com/20138947/136924746-acc471df-67c4-46dd-843e-803c860bc4a1.png)
结果一样我想问问怎么解决这个问题!不想修改sql语句!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading datax.py and reproducing the MySQL-to-Hive transfer described in the issue, including the 13-hour timestamp shift. Trace the timezone handling between the source and destination and verify any proposed configuration-based fix with the supplied table and values, without changing the SQL statement.

Written by the indexing model from the issue text.

Assessment

Tech stack
mysql
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.