[
https://issues.apache.org/jira/browse/FLINK-8169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328695#comment-17328695
]
Flink Jira Bot commented on FLINK-8169:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Document timestamp and timezone behavior for Table API & SQL
> ------------------------------------------------------------
>
> Key: FLINK-8169
> URL: https://issues.apache.org/jira/browse/FLINK-8169
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Timo Walther
> Priority: Major
> Labels: stale-major
>
> {{java.sql.Date}}, {{java.sql.Time}}, and {{java.sql.Timestamp}} are timezone
> dependent. However, in Flink's Table & SQL API we remove this dependency and
> work with UTC timestamps internally. It should be documented how windows use
> the timestamps in different timezones for event-time. The behavior for
> processing-time should be explained as well. What is the result if I cast
> both timestamps to Long, String, or output them to a DataSet/DataStream?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
