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

bug(postgres-cdc): Debezium cannot handle early timestamp #16895

Open
KeXiangWang opened this issue May 23, 2024 · 2 comments
Open

bug(postgres-cdc): Debezium cannot handle early timestamp #16895

KeXiangWang opened this issue May 23, 2024 · 2 comments
Labels
type/bug Something isn't working

Comments

@KeXiangWang
Copy link
Contributor

KeXiangWang commented May 23, 2024

Describe the bug

With time.precision.mode=adaptive_time_microseconds, Debezium's postgres cdc connector will convert early timestamp "0001-01-01 00:00:00" to "0001-12-29 23:42:28 BC" Not sure the root cause. The timestamp close now are handled correctly.

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

@KeXiangWang KeXiangWang added the type/bug Something isn't working label May 23, 2024
@github-actions github-actions bot added this to the release-1.10 milestone May 23, 2024
@StrikeW
Copy link
Contributor

StrikeW commented May 23, 2024

It is good findings, but I think the problem may not need to fix, the use case is very rare.

@KeXiangWang
Copy link
Contributor Author

KeXiangWang commented May 23, 2024

It is good findings, but I think the problem may not need to fix, the use case is very rare.

Let's at least note it down here.

@fuyufjh fuyufjh removed this from the release-1.10 milestone Jul 10, 2024
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