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

Posted to issues@flink.apache.org by "Zhenghua Gao (Jira)" <ji...@apache.org> on 2019/12/02 03:30:00 UTC

[jira] [Updated] (FLINK-14599) Support precision of TimestampType in blink planner

     [ https://issues.apache.org/jira/browse/FLINK-14599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhenghua Gao updated FLINK-14599:
---------------------------------
    Release Note: 
[incompatible change] Disable conversion between Timestmap and long in parameters and results of UDXs
http://mail-archives.apache.org/mod_mbox/flink-dev/201911.mbox/%3cCAL5q=a5dsm9+QEZ0eVG-gS7qR6ippRRnRiYAQFaGwNU_Spe6OA@mail.gmail.com%3e

> Support precision of TimestampType in blink planner
> ---------------------------------------------------
>
>                 Key: FLINK-14599
>                 URL: https://issues.apache.org/jira/browse/FLINK-14599
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Planner
>            Reporter: Zhenghua Gao
>            Assignee: Zhenghua Gao
>            Priority: Major
>
> Since FLINK-14080 introduced an internal representation(SqlTimestamp) of TimestampType with precision. This subtask will replace current long with SqlTimestamp, and let blink planner support precision of TimestampType.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)