[
https://issues.apache.org/jira/browse/FLINK-16584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319426#comment-17319426
]
Kurt Young commented on FLINK-16584:
------------------------------------
with 1.13, you can convert Long to TIMESTAMP_LTZ with builtin function
TO_TIMESTAMP_LTZ. This type has builtin support with conversion between Long. I
think it's enough to meet this requirement and I would close this issue.
> Whether to support the long type field in table planner when the source is
> kafka and event time field's type is long
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-16584
> URL: https://issues.apache.org/jira/browse/FLINK-16584
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: hehuiyuan
> Priority: Minor
>
> For rowtime function , the field type may be long or timestamp .
> But the event time field type is only timestamp when use kafka connect.
> Some validations (for example ,when create kafka table source ) are not
> allowed long.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
