Details
-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
False
-
Undefined
Description
We met the issue that DATE column was truncated incorrectly with database.useCursorFetch": "true".
org.apache.kafka.connect.errors.ConnectException: Unexpected format for DATE column: �^G^C^\ at io.debezium.connector.mysql.AbstractReader.wrap(AbstractReader.java:230) at io.debezium.connector.mysql.AbstractReader.failed(AbstractReader.java:207) at io.debezium.connector.mysql.SnapshotReader.execute(SnapshotReader.java:831) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
It's fixed in a later release:
https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-19.html
When retrieving TIME values using ResultSet.getTimestamp(), the fractional seconds are truncated when useCursorFetch=true. This patch corrects the problem by fixing the TIME value decoding in the MysqlBinaryValueDecoder. It also corrects some inconsistencies in formatting the fractional seconds when returning the TIME values as strings. (Bug #30119545, Bug #96383)
