[FLINK-20162] Fix time zone problems for some time related functions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Component/s: Table SQL / API
• Labels: auto-unassigned
• Assignee: Unassigned
• Reporter: Jark Wu
• Created: 14/Nov/20 10:17
• Updated: 29/Apr/21 15:22
• Resolved: 29/Apr/21 15:22

Description

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.

Issue Links

• is related to: FLINK-20387 Support defining event time attribute on TIMESTAMP_LTZ column
• is related to: FLINK-18206 The timestamp is displayed incorrectly
• is related to: FLINK-11223 Time zone problem for time processing function
• is related to: FLINK-16938 SqlTimestamp has lag when convert long to Timestamp
• is related to: FLINK-16889 Support converting BIGINT to TIMESTAMP for TO_TIMESTAMP function
• is related to: FLINK-19757 TimeStampData can cause time inconsistent problem
• relates to: FLINK-21617 FLIP-162: Consistent Flink SQL time function behavior

Sub-Tasks

• The LOCALTIME/LOCALTIMSTAMP functions should use session time zone: Closed