Open KeXiangWang opened 1 month ago
It is good findings, but I think the problem may not need to fix, the use case is very rare.
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.
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