[FLINK-14599] Support precision of TimestampType in blink planner

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.10.0
• Component/s: Table SQL / Planner

Release Note

[incompatible change] Disable conversion between Timestmap and long in parameters and results of UDXs
http://mail-archives.apache.org/mod_mbox/flink-dev/201911.mbox/%3cCAL5q=[e-mail]%3e

• Assignee: Zhenghua Gao
• Reporter: Zhenghua Gao
• Created: 04/Nov/19 10:09
• Updated: 15/Jan/20 13:06
• Resolved: 02/Dec/19 08:11

Description

Since FLINK-14080 introduced an internal representation(SqlTimestamp) of TimestampType with precision. This subtask will replace current long with SqlTimestamp, and let blink planner support precision of TimestampType.

Issue Links

• is related to: FLINK-14645 Data types defined in DDL will lose precision and nullability when converting to properties
• is related to: FLINK-15602 Blink planner does not respect the precision when casting timestamp to varchar
• relates to: FLINK-14696 Support precision of TimestampType in built-in SQL functions and operators