[
https://issues.apache.org/jira/browse/FLINK-14080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenghua Gao updated FLINK-14080:
-
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.
was:Now, blink planner only support precision is 3, we need support more
because default precision is 6.
> 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
>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)
