You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kurt Young (Jira)" <ji...@apache.org> on 2019/11/04 10:07:00 UTC
[jira] [Closed] (FLINK-14080) Introduce SqlTimestamp as internal
representation for high precision of timestamp
[ https://issues.apache.org/jira/browse/FLINK-14080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Young closed FLINK-14080.
------------------------------
Resolution: Fixed
fixed via: 845fb95e633931eee4ff86a82c886050f318a32a
We need another Jira to modify the code generation logic to support high precision timestamp.
> Introduce SqlTimestamp as internal representation for high precision of timestamp
> ---------------------------------------------------------------------------------
>
> Key: FLINK-14080
> URL: https://issues.apache.org/jira/browse/FLINK-14080
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Reporter: Jingsong Lee
> Assignee: Zhenghua Gao
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)