Timestamp differs when queried from presto and trino with mysql databases.

[naveenbussari]

We currently have presto running on kubernetes.
We are exploring migrating from presto to trino(in the same kubernetes cluster)

We are facing issues with the timestamp specifically with the mysql database.
Trino is returning the values in timestamp column in UTC where as the actual mysql db stores timestamp in (IST) Asia/Kolkata timezone.

trino version: 432

The actual mysql databases stores the timestamp in IST ( Asia/Kolkata )

When queried from Presto , the data is returned as it is in mysql db i.e., Asia/Kolkata timezone.

When queried from Trino, the data is returned in UTC timezone.

I tried adding the property serverTimezone=Asia/Kolkata . But this didn't work.

When I use the AT TIME ZONE clause with the query in trino it works,

This is happening only with mySQL databases but not postgreSQL.
I have checked with multiple catalogs and databases.
In postgres databases, the results are in IST in Presto as well as Trino as it is stored in the actual postgres database.

How can I get the values in timestamp column in Asia/Kolkata timezone?

[martint]

cc @hashhar @ebyhr

[naveenbussari]

@ebyhr
could you please help here