[
https://issues.apache.org/jira/browse/FLINK-14099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16931999#comment-16931999
]
Canbin Zheng commented on FLINK-14099:
--------------------------------------
+1. I think Computed column is a more general and better way. Maybe in future
we can provide some generic and easy-use built-in functions for converting
different rowtime field type into standard SQL Timestamp.
In production environment, rowtime field from source usually has many different
modes, cases like
1. second(String): "1568774938"
2. second(Long): 1568774938
3. millisecond(String): "1568774938143"
4. millisecond(Long): 1568774938143
5. custom date format:
yyyyMMddHHmmss: "20190918112311"
yyyy-MM-dd HH:mm:ss "2019-09-18 11:23:11"
yyyy-MM-dd HH:mm:ss.SSS "2019-09-18 11:23:11.131"
> SQL supports timestamp in Long
> ------------------------------
>
> Key: FLINK-14099
> URL: https://issues.apache.org/jira/browse/FLINK-14099
> Project: Flink
> Issue Type: New Feature
> Reporter: Zijie Lu
> Priority: Major
>
> The rowtime only supports sql timestamp but not long. Can the rowtime field
> supports long?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
