Skip to content
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

MySQL CDC datetime and RW timestamp type incompatibility #13582

Closed
cyliu0 opened this issue Nov 22, 2023 · 2 comments
Closed

MySQL CDC datetime and RW timestamp type incompatibility #13582

cyliu0 opened this issue Nov 22, 2023 · 2 comments
Labels
type/bug Something isn't working
Milestone

Comments

@cyliu0
Copy link
Collaborator

cyliu0 commented Nov 22, 2023

Describe the bug

I tried to use RW timestamp to sync MySQL datetime from MySQL CDC. But I got the following result. Other normal values like 2001-01-01 23:59:59 can be synced properly.

In MySQL:

mysql> select c_datetime from mysql_all_types;
+---------------------+
| c_datetime          |
+---------------------+
| 1000-01-01 00:00:00 |
| 1000-01-01 00:00:00 |
| 9999-12-31 23:59:59 |
+---------------------+
3 rows in set (0.00 sec)

In RW:

dev=> select c_datetime from mysql_all_types;
       c_datetime        
-------------------------
 
 1978-01-11 21:31:40.799
 
(3 rows)

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

nightly-20231121

Additional context

No response

@cyliu0 cyliu0 added the type/bug Something isn't working label Nov 22, 2023
@github-actions github-actions bot added this to the release-1.5 milestone Nov 22, 2023
@lmatz
Copy link
Contributor

lmatz commented Nov 22, 2023

cc: @xiangjinwu,

Is it related to the PG CDC's ce/epoch issue #13486?

@xiangjinwu
Copy link
Contributor

No. It is related to #8359 (comment) (#6318)

Other normal values like 2001-01-01 23:59:59 can be synced properly.

#8359 (comment)

Note that if you are ingesting data of type timestamp or timestampz in RisingWave, the upstream value must be in the range of [1973-03-03 09:46:40, 5138-11-16 09:46:40] (UTC). The value may be parsed and ingested incorrectly without warning.

@xiangjinwu xiangjinwu closed this as not planned Won't fix, can't repro, duplicate, stale Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants