Support CTAS into Iceberg with timestamp(3)

See original GitHub issue

Trino uses 3 digits of subsecond precision in Date and time functions, but Iceberg expects timestamp with 3 digits of subsecond precision.

As a result we can’t create Iceberg table from Trino

create table iceberg.examples.test
as select now() as n;

Exception: Timestamp precision (3) not supported for Iceberg. Use "timestamp(6) with time zone" instead.

Is it possible to make default precision configurable or allow use of Timestamp with precision (3) for Iceberg tables?

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

daniil-dubincommented, May 24, 2022

@findepi we have thousands of scripts (as well as many other companies I believe do) that we are migrating to iceberg automatically. We can’t just mechanically replace all the occurrences of now() or current_timestamp() with current_timestamp(6) as it may brake other places unrelated to iceberg and requires semantical analysis of the script. It will take hundreds of hours of work for the data developers to change the scripts and validate them. We are hacking iceberg connector to add conversion there but we’d like to avoid doing it as much as possible.

1reaction

sshkvarcommented, Jan 20, 2021

I have renamed this issue and started discussion in slack