You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/11/14 10:18:00 UTC

[jira] [Updated] (FLINK-20162) Fix time zone problems for some time related functions

     [ https://issues.apache.org/jira/browse/FLINK-20162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jark Wu updated FLINK-20162:
----------------------------
    Summary: Fix time zone problems for some time related functions  (was: Fix time zone problems form some time related functions)

> Fix time zone problems for some time related functions
> ------------------------------------------------------
>
>                 Key: FLINK-20162
>                 URL: https://issues.apache.org/jira/browse/FLINK-20162
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / API
>            Reporter: Jark Wu
>            Priority: Major
>             Fix For: 1.13.0
>
>
> Currently, lots of time related functions are returning {{TIMESTAMP}} type, including {{PROCTIME()}}, {{NOW()}}, {{LOCALTIMESTAMP}},etc. However, they should return {{TIMESTAMP WIHT LOCAL TIME ZONE}} type. The session time zone will be used when converting {{TIMESTAMP WITH LOCAL TIME ZONE}} to string, but not for {{TIMESTAMP}} type.
> That's why many users report the result is incorrect with 8 hours when converting these functions to string.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)