Hi, I'm afraid you do indeed need to have a separate window for each timezone, yes. You can probably use an hourly window to pre-aggregate the results and then have specific daily windows for the different timezones with aggregate different (pre-aggregated) hourly results.
Does that work for your case? Best, Aljoscha > On 16. Aug 2017, at 10:28, Biplob Biswas <revolutioni...@gmail.com> wrote: > > Hi Alex, > > Your problem sounds interesting and I have always found dealing with > timestamps cumbersome. > > Nevertheless, what I understand is that your start and end timsstamp for > American and European customers are based on their local clock. > > For ex the start and end timestamp of 12 AM - 12 AM in america would be > different for the same time in europe (also would be different across > timezones with the continent as well) > > What I can think of right now is to define your start and end timestamp from > a reference timezone like take UTC as your reference and define one time > globally. It solves your problem of creating multiple windows for all > timezones but may not satisfy your customers need as the 1 day would be > defined not from midnight anymore (if thats what you need). > > Otherwise, AFAIK about Flink ...you would have to define the timewindows for > all the timezones u need, but the experts here may point out to some better > solution. > > Regards, > Biplob > > > > > > -- > View this message in context: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Time-zones-problem-tp14907p14925.html > Sent from the Apache Flink User Mailing List archive. mailing list archive at > Nabble.com.
