Hi Biplob, Yes unix timestamp is what I¹m using now.
But the problem is that a time window like '1 day' is defined using different start-end timestamps for users in different time zones Let me try to draw it |----1------2-----3-----4-------| 1 and 3 - time frames for European users 2 and 4 - time frames for American users Now we need to calculate some metrics, like sum or max of call durations using time window '1 day¹. Evidently they are different for different time zones. Should I create an aggregation window for each and every time zone to cover that? For each possible reporting time interval? Is it how this can be achieved with Flink? Thank you, Alex On 8/15/17, 1:09 AM, "Biplob Biswas" <revolutioni...@gmail.com> wrote: >Regarding timezones, you should probably convert your time to the unix >timestamp which will be consistent all over the world, and then you can >create your window based on this timestamp. > > > > > >-- >View this message in context: >http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Time-z >ones-problem-tp14907p14911.html >Sent from the Apache Flink User Mailing List archive. mailing list >archive at Nabble.com. > ________________________________ CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential information of Five9 and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Five9 and/or its affiliated entities.
