[FLINK-14080] Introduce SqlTimestamp as internal representation for high precision of timestamp

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.10.0
• Component/s: Table SQL / Planner
• Labels: pull-request-available
• Assignee: Zhenghua Gao
• Reporter: Jingsong Lee
• Created: 16/Sep/19 06:14
• Updated: 04/Nov/19 10:06
• Resolved: 04/Nov/19 10:06

Description

Timestamp values have a precision in fractional seconds that range from 0 to 9. For example, a precision of 0 means that no fractional seconds are stored, 3 means that the timestamp stores milliseconds, and 9 means a precision of nanoseconds. 0 is the minimum precision, and 9 is the maximum.

Now, blink planner represent Timestamp values as Long(milliseconds) and  only support precision is 3, we need support more precision Timestamp values.

Issue Links

• links to: GitHub Pull Request #10035