[
https://issues.apache.org/jira/browse/FLINK-14696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhenghua Gao updated FLINK-14696:
---------------------------------
Description:
Many built-in SQL functions and operators use long as internal representation
of Timestamp type and only support millisecond precision. This ticket will
check fix it and let them support nanosecond precision. The related SQL
functions and operators are:
* timestamp compare
* timestamp +/- interval
* extract function
* timestampadd/timestampdiff function
* to_timestamp function
* timestamp cast
was:
Many built-in SQL functions and operators use long as internal representation
of Timestamp type and only support millisecond precision. This ticket will
check fix it and let them support nanosecond precision. The related SQL
functions and operators are:
* timestamp compare
* timestamp +/- interval
* extract function
* timestampadd/timestampdiff
* to_timestamp
* timestamp cast
> Support precision of TimestampType in built-in SQL functions and operators
> --------------------------------------------------------------------------
>
> Key: FLINK-14696
> URL: https://issues.apache.org/jira/browse/FLINK-14696
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Reporter: Zhenghua Gao
> Priority: Major
>
> Many built-in SQL functions and operators use long as internal representation
> of Timestamp type and only support millisecond precision. This ticket will
> check fix it and let them support nanosecond precision. The related SQL
> functions and operators are:
> * timestamp compare
> * timestamp +/- interval
> * extract function
> * timestampadd/timestampdiff function
> * to_timestamp function
> * timestamp cast
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
