You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by "WuChongYong (via GitHub)" <gi...@apache.org> on 2024/12/31 06:26:06 UTC
[I] There is a bug in non-standard timestamp values [flink-cdc]
WuChongYong opened a new issue, #3827:
URL: https://github.com/apache/flink-cdc/issues/3827
### Please don't check the box below
- [X] I'm aware that bugs and new features should be reported on [Apache Jira](https://issues.apache.org/jira) or Flink mailing list (dev@flink.apache.org) instead of here
### Again, please don't check the box below
- [X] I'm aware that new issues on GitHub will be ignored and automatically closed.
### 请不要勾选以下选项
- [X] 我已知悉缺陷和新功能需要在 [Apache Jira](https://issues.apache.org/jira) 或 Flink 邮件列表（dev@flink.apache.org）中反馈，而不是在这里创建新 issue。
### 也请不要勾选以下选项
- [X] 我已知悉 GitHub 上的新 issue 会被忽略且自动关闭。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@flink.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] There is a bug in non-standard timestamp values [flink-cdc]
Posted by "leonardBang (via GitHub)" <gi...@apache.org>.
leonardBang closed issue #3827: There is a bug in non-standard timestamp values
URL: https://github.com/apache/flink-cdc/issues/3827
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] There is a bug in non-standard timestamp values [flink-cdc]
Posted by "WuChongYong (via GitHub)" <gi...@apache.org>.
WuChongYong commented on issue #3827:
URL: https://github.com/apache/flink-cdc/issues/3827#issuecomment-2566170058
The data in a certain (timestamp type) time field of the table in the source MySQL is 0002-11-30 08:05:43, and the timestamp that Flink CDC should output is -62075462057000L, but the actual timestamp output by Flink CDC is 1038643543000L, which is different from the value in the data source
Data such as:
INSERT INTO testdb.test_datetime
(id, datetime_col)
VALUES('1', '0002-11-30 08:05:43');
INSERT INTO testdb.test_datetime
(id, datetime_col)
VALUES('2', '0022-11-30 08:05:43');
INSERT INTO testdb.test_datetime
(id, datetime_col)
VALUES('3', '0222-11-30 08:05:43');
Only the parsing of 0222-11-30 08:05:43 is correct, which means that there will be problems when the prefix has two or more 0s
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org