alibaba / alibaba/DataX

OTSwriter中,针对OTS中自增的主键给null值报脏数据错误

Open
#1,355 0 comments 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

![image](https://user-images.githubusercontent.com/65753320/165707011-d3060246-dff0-40c1-88b3-b604b41a4882.png)

sql长这样
select user_id ,user_name ,operation ,null as auto_key, UNIX_TIMESTAMP(create_time) as create_time ,\nip ,`method` as methods,params ,\nUNIX_TIMESTAMP(update_time) as update_time from bos_log
writer中的key字段长这样
![image](https://user-images.githubusercontent.com/65753320/165707095-48853084-371b-4acb-9fde-e443eac6a8a7.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the shown SQL and OTSwriter key configuration first, then trace OTSwriter's handling of a null value for an auto-increment primary key. Done means this case no longer reports dirty data and the resulting write behavior is verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, sql
Domain
databases
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.