Inserting into DateTime64(9) column gave incorrect results #599
Description
Describe the bug
When we use the ClickHouse sink connector to ingest a timestamp into a DateTime64(9) column, we found that it gave the wrong values (see screenshot - these should all have been 2025 dates). Changing the column to DateTime64(3) resolved the issue for us
Steps to reproduce
- Create a table with a DateTime64(9) column
- Create a sink connector to ingest into the table using the default ISO formatted date
Expected behaviour
The date in the clickhouse table should be the same as in Kafka message
Actual behaviour
The date in clickhouse table is in year 1970