[ 
https://issues.apache.org/jira/browse/FLINK-21803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leonard Xu resolved FLINK-21803.
--------------------------------
    Fix Version/s: 1.13.0
       Resolution: Implemented

Since flink 1.13 you can define time attribute on TIMESTAMP_LTZ column and then 
the window calculation will consider the DST time.

[1][https://ci.apache.org/projects/flink/flink-docs-release-]1.13/docs/dev/table/concepts/timezone/#daylight-saving-time-support

> Tumbling / Sliding windows are unaware of daylight savings time
> ---------------------------------------------------------------
>
>                 Key: FLINK-21803
>                 URL: https://issues.apache.org/jira/browse/FLINK-21803
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>    Affects Versions: 1.12.2
>            Reporter: Craig Smoothey
>            Priority: Minor
>              Labels: auto-deprioritized-major
>             Fix For: 1.13.0
>
>
> It is currently possible to specify an "offset" for tumbling / sliding 
> windows. The offset is however immutable. This creates a problem for 
> aggregations that have to be performed in a timezone which utilises daylight 
> savings time for half of the year. For example. If one is aggregating data by 
> day in the New York time zone, then for half of the year, the offset is 5 
> hours (relative UTC) and for the other half of the year, the offset is 4 
> hours (relative UTC). There is no way to construct tumbling / sliding windows 
> to specify daylight savings time behaviour. It would be helpful if there was 
> a constructor for tumbling / sliding windows to specify the timezone that the 
> aggregation must be performed in (default = UTC). The tumbling / sliding 
> window would then be required to automatically change the offset depending on 
> whether daylight savings time is active or not for the specified time zone. 
> My application is using the DataStream API.



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

Reply via email to