[
https://issues.apache.org/jira/browse/FLINK-21978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17309426#comment-17309426
]
Jark Wu commented on FLINK-21978:
---------------------------------
The current implementation of casting between numeric and TIMESTAMP_LTZ treats
all numeric as seconds. We also considered treat BIGINT as millseconds and INT
as seconds for better consistent in Flink. However, it seems other database
vendors didn't do so. In the other hand, we think functions is more expressive
and explainable than CAST. That's why we disable this casting temporarily.
> 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)
