Closed gegl closed 11 months ago
Hello! @slvrtrn I had a similar issue that you can find here. I understand that it should have been solved with Metabase version 0.47, but I'm already using 0.47.1 version and the issue persist. Should it be re-opened?
@brendavarguez, if this issue still persists on 1.2.1, feel free to re-open this issue with more details.
Describe the bug
When a ClickHouse DateTime is associated with a TimeZone after converting from UTC to TimeZone in a ClickHouse view, the resulting type DateTime('Europe/Berlin') is not mapped to Metabase type/DateTime. It falls back on type/*. This negatively affects UIs for filtering in Metabase.
Steps to reproduce
Use any column where a TimeZone version is applied eg. toTimeZone(, 'Europe/Berlin') :
The resulting ClickHouse data type is
DateTime('Europe/Berlin')
according toDESC <table name>
When passed throuh the metabase-clickhouse-driver it is mapped to
type/*
Expected behaviour
DateTime('Europe/Berlin') is mapped to type/DateTime
Configuration
Environment
ClickHouse server
CREATE TABLE
statements for tables involved: