You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jingsong Lee (Jira)" <ji...@apache.org> on 2019/09/26 03:47:00 UTC

[jira] [Commented] (FLINK-14080) Support precision of TimestampType

    [ https://issues.apache.org/jira/browse/FLINK-14080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938237#comment-16938237 ] 

Jingsong Lee commented on FLINK-14080:
--------------------------------------

[~jark] Can you assign this ticket to [~docete] ?

> Support precision of TimestampType
> ----------------------------------
>
>                 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
>             Fix For: 1.10.0
>
>
> 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)