[ https://issues.apache.org/jira/browse/FLINK-21978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17309326#comment-17309326 ]
Leonard Xu commented on FLINK-21978: ------------------------------------ [~twalthr] Besides conversion class may cause confusion, another confusion source is that the `FROM_UNIXTIME(numeric [,foramtString])` treats numeric value in seconds. And we invested some main DB vendors like snowflake (TO_TIMESTAMP_LTZ,TO_TIMESTAMP_NTZ, FROM_UNIXTIME), oracle(FROM_UNIXTIME), most of them treat BIGINT as seconds > Disable cast conversion between Numeric type and TIMESTAMP_LTZ type > ------------------------------------------------------------------- > > Key: FLINK-21978 > URL: https://issues.apache.org/jira/browse/FLINK-21978 > Project: Flink > Issue Type: Sub-task > Components: Table SQL / Planner > Affects Versions: 1.13.0 > Reporter: Leonard Xu > Assignee: Leonard Xu > Priority: Major > Labels: pull-request-available > > Currently we has supported the cast conversion between Numeric type and > TIMESTAMP_LTZ type, we suppose the numeric value e.g `Long type 1000L` as > epoch seconds and then cast to TIMESTAMP_LTZ, but the java.lang.Long is a > conversion class of `LocalZonedTimestampType` and treats as milliseconds. > To avoid the inconsistency, we should disable it and encourage user to use > `TO_TIMESTAMP_LTZ(numeric, precisoon)` function. -- This message was sent by Atlassian Jira (v8.3.4#803005)