You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue is present on 25.8, 26.1 altinityalntalya, but not present on 25.8, 26.1 upstream.
Reading an Iceberg table with a TIME column via ClickHouse returns different units depending on the partition spec, even though the schema and data are identical.
The same values are returned as microseconds in one case and seconds in another.
Does it reproduce on the most recent release?
Yes
How to reproduce
Create two Iceberg tables with the same schema and data
Describe what's wrong
Issue is present on 25.8, 26.1 altinityalntalya, but not present on 25.8, 26.1 upstream.
Reading an Iceberg table with a TIME column via ClickHouse returns different units depending on the partition spec, even though the schema and data are identical.
The same values are returned as microseconds in one case and seconds in another.
Does it reproduce on the most recent release?
Yes
How to reproduce
Create two Iceberg tables with the same schema and data
Schema includes a TIME column (TimeType)
Only difference is the partition spec (empty vs identity partition on string column (partition by time column did not work for me Can not read from Iceberg table that was partitioned by Time column ClickHouse/ClickHouse#94685)
Read both tables via DataLakeCatalog
Non partitioned table:
Partitioned table:
Expected behavior
Partition spec differences must not change the semantic representation of Iceberg TIME values.
Error message and/or stacktrace
No response
Additional context