> --
> 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.
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.
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 - t
-zones-problem-tp14907p14911.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at
Nabble.com.
Hello everybody,
I’m exploring Flink options to build statistics engine for call center solution.
One thing I’m not sure how to implement.
Currently have the following jobs in the architecture.
Job #1 – is for matching start and end events and calculate durations. Like
having call started and c
