[
https://issues.apache.org/jira/browse/FLINK-16889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072467#comment-17072467
]
Kurt Young edited comment on FLINK-16889 at 4/1/20, 7:24 AM:
-------------------------------------------------------------
I'm afraid that users maybe expect the timestamp will be generated using local
timezone.
was (Author: ykt836):
I'm afraid that users maybe expect the timestamp will be generated using local
timestamp.
> Support converting BIGINT to TIMESTAMP for TO_TIMESTAMP function
> ----------------------------------------------------------------
>
> Key: FLINK-16889
> URL: https://issues.apache.org/jira/browse/FLINK-16889
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API, Table SQL / Planner
> Reporter: Jark Wu
> Priority: Major
> Labels: usability
> Fix For: 1.11.0
>
>
> Many users reported that it is not possible for now to define an event-time
> field or watermark on a BIGINT column.
> Impala supports to convert BIGINT into TIMESTAMP value using TO_TIMESTAMP()
> function [1]. The BIGINT argument represents the number of seconds past the
> epoch.
> I think it makes sense to support this for Flink's TO_TIMESTAMP(). It is the
> converse of the UNIX_TIMESTAMP() function, which produces a BIGINT
> representing the number of seconds past the epoch.
> [1]:
> https://impala.apache.org/docs/build/html/topics/impala_datetime_functions.html#datetime_functions__to_timestamp
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
