Presto JDBC: Timezone displays incurrect even after setting -Duser.timezone=+0800

Could you specify your presto db jdbc driver version?

It's 0.213, same issue using 0.211, 0.214. I think it's not about the jdbc version. Please check this out:

-- _col0                              _col1
-- 2018-11-30 01:24:35     true
select
    now(),
    now() > cast('2018-11-30 09:18:10' as timestamp);

It works if use Java code (VM options: -Duser.timezone=+0800)

ResultSet result = stat.executeQuery("select now()");
while (result.next()) {
    System.out.println(result.getString(1));
}
// 2018-11-30 09:23:26.447 +08:00

I reproduced the issue. Follow https://youtrack.jetbrains.com/issue/DBE-7504 to get updates

using the 2021.2 RC this does not appear to be fixed by DBE-7504

Alexga,

Everything is working as expected in 2021.2 RC.

Output of Presto CLI:

Output of DataGrip 2021.2 RC:

Could you provide an example to reproduce your issue?

Appreciate the follow up. Apologize for not adding an example in the first place.

I'm running 2021.2 (no longer the RC) at this point but am still able to recreate. 

output from CLI:

Output from DataGrip 2021.2:

Alexga,

I see. Could you leave a comment in https://youtrack.jetbrains.com/issue/DBE-7504 and attach IDE and SQL logs for investigation?

vasily chernov, I see you copied the above over, do you need server logs as well? happy to provide them if needed

Alexga,  it would be great if you provide exact server version, server timezone, your client timezone and JDBC driver version. Could you do that?

current version: 

2021-07-29T21:46:03.594Z INFO main io.trino.server.Server Trino version: 359

server timezone:

2021-07-29T21:52:32.133Z INFO main Bootstrap sql.forced-session-time-zone ---- ---- User session time zone overriding value sent by client

and

trino> select current_timezone();
 _col0
-------
 UTC
(1 row)

Query 20210729_215302_00000_thvmf, FINISHED, 1 node
Splits: 1 total, 1 done (100.00%)
0.56 [0 rows, 0B] [0 rows/s, 0B/s]

client timezone:

no vm options

jdbc driver:

This is the provided driver, but I've also tried it with ver 359

It seems Datagrip 2023.2.1 bring this bug back.

Trino Server: 420

JDBC: 407

select current_timezone()
Asia/Shanghai

select current_timestamp  
2023-08-22 01:22:43.544 <-- this is incorrect, it should be `2023-08-22 09:18:02.885 Asia/Shanghai`

DataGrip 2022.3.3 works as expected.

Can I ask you to report it?
https://youtrack.jetbrains.com/newIssue?project=DBE

Bear0king

I have reproduced the part where the timezone was truncated from the output when running 'select current_timestamp', but I could not spot any issues with the time returned by the current_timezone() function. I have this issue reported here, so feel free to add your examples there, and we'll sum it up