You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (Jira)" <ji...@apache.org> on 2021/01/20 14:46:00 UTC

[jira] [Commented] (FLINK-21055) Allow TIMESTAMP WITH LOCAL TIME ZONE (Instant) to be rowtime

    [ https://issues.apache.org/jira/browse/FLINK-21055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268616#comment-17268616 ] 

Timo Walther commented on FLINK-21055:
--------------------------------------

[~vlaaad] we just started with a discussion on the mailing list around time/timestamps in Flink, feel free to join there as well:

https://lists.apache.org/thread.html/rb5ab3fa83a48f2b88ff9cf2fdf2f483bfbb04d8b380b418a99526836%40%3Cdev.flink.apache.org%3E

> Allow TIMESTAMP WITH LOCAL TIME ZONE (Instant) to be rowtime
> ------------------------------------------------------------
>
>                 Key: FLINK-21055
>                 URL: https://issues.apache.org/jira/browse/FLINK-21055
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Planner, Table SQL / Runtime
>            Reporter: Vladislav Protsenko
>            Priority: Major
>
> Currently, when trying to use Instants as "columns" in SQL as rowtime, planner fails to validate graph with the following exception:
> The rowtime attribute can only replace a field with a valid time type, such as Timestamp or Long. But was: Instant
> I think Instant is a more useful time type than Timestamp or Long, so it would be great if that was supported.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)