Closed wiseliu-finaccel closed 3 weeks ago
clickhouse-connect
just passes the file directly to ClickHouse, which does all parsing. You should check the main ClickHouse repository for similar issues, and open a new one there if it hasn't already been filed (I vaguely recall something similar). You can create a reproducible example for a new issue using the official ClickHouse CLI client.
Describe the bug
Failed to insert CSV file if the file contains 16 digit epoch to column with DateTime64(6) using clickhouse-connect python driver
Steps to reproduce
Expected behaviour
CSV file inserted successfully
Code example
clickhouse-connect and/or ClickHouse server logs
Configuration
Environment
ClickHouse server
CREATE TABLE
statements for tables involved:(
timestamp
DateTime64(6, 'Asia/Jakarta') CODEC(DoubleDelta, ZSTD),instanceName
LowCardinality(String) CODEC(ZSTD),username
LowCardinality(String) CODEC(ZSTD),host
String DEFAULT '' CODEC(ZSTD),connectionid
UInt64 CODEC(T64, ZSTD),queryid
UInt64 CODEC(T64, ZSTD),operation
LowCardinality(String) CODEC(ZSTD),database
LowCardinality(String) CODEC(ZSTD),object
String CODEC(ZSTD),retcode
Int8 CODEC(T64, ZSTD), )