Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

presto timestamp bug #15772

Open
rzj-bigdata opened this issue Mar 4, 2021 · 3 comments
Open

presto timestamp bug #15772

rzj-bigdata opened this issue Mar 4, 2021 · 3 comments
Labels

Comments

@rzj-bigdata
Copy link

select timestamp '1946-05-15 00:00:00';
Query 20210304_070605_05374_mzzm9 failed: line 1:8: '1946-05-15 00:00:00' is not a valid timestamp literal

@iceted
Copy link

iceted commented Mar 6, 2021

in my experience timestamps are very broken in Presto. This is the best explanation I found about it: trinodb/trino#37 and it appears it the bug was fixed in recent versions of the Trino distribution of Presto: https://trino.io/docs/current/release/release-341.html. Would you like to backport that change?

@v-jizhang
Copy link
Contributor

Yes, it's on our list now. Thanks.

@v-jizhang
Copy link
Contributor

@rzj-bigdata Seems it has been fixed already. Here is my test:

presto> select timestamp '1946-05-15 00:00:00';
          _col0          
-------------------------
 1946-05-15 00:00:00.000 
(1 row)

Query 20210319_150141_00003_53afs, FINISHED, 1 node
Splits: 17 total, 17 done (100.00%)
0:00 [0 rows, 0B] [0 rows/s, 0B/s]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants