[
https://issues.apache.org/jira/browse/FLINK-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413519#comment-15413519
]
Aditi Viswanathan commented on FLINK-4282:
------------------------------------------
Also when we want to assign time zones, system.currentTimeMillis() will
always give the epoch time, irrespective of time zones. So we'd have to use
the epoch time, correct window size and triggering time as well as assign
the element to the specified time zone.
This is the same case as the scenario I mentioned with the 5 seconds,
because the processing time will be in UTC and won't directly fall into the
other time zone buckets. That's why I've modified the triggering so that
whatever the offset, it will still trigger correctly after the specified
window size.
Aditi Viswanathan | +91-9632130809
Data Engineer,
[24]7 Customer Ltd.
On Tue, Aug 9, 2016 at 6:35 PM, Aljoscha Krettek (JIRA) <j...@apache.org>
> Add Offset Parameter to WindowAssigners
> ---------------------------------------
>
> Key: FLINK-4282
> URL: https://issues.apache.org/jira/browse/FLINK-4282
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Reporter: Aljoscha Krettek
>
> Currently, windows are always aligned to EPOCH, which basically means days
> are aligned with GMT. This is somewhat problematic for people living in
> different timezones.
> And offset parameter would allow to adapt the window assigner to the timezone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
