[
https://issues.apache.org/jira/browse/FLINK-8169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335492#comment-17335492
]
Leonard Xu commented on FLINK-8169:
-----------------------------------
resolved in FLINK-22177
[https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/table/concepts/timezone/]
> 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)
