Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5BF03200CF3 for ; Tue, 15 Aug 2017 07:00:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5A5D61663A7; Tue, 15 Aug 2017 05:00:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A4A9D1663A5 for ; Tue, 15 Aug 2017 07:00:44 +0200 (CEST) Received: (qmail 14996 invoked by uid 500); 15 Aug 2017 05:00:38 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list user@flink.apache.org Received: (qmail 14979 invoked by uid 99); 15 Aug 2017 05:00:38 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Aug 2017 05:00:38 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 2B6C91A170D for ; Tue, 15 Aug 2017 05:00:38 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.299 X-Spam-Level: * X-Spam-Status: No, score=1.299 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id G1Cpj2H3iOLz for ; Tue, 15 Aug 2017 05:00:31 +0000 (UTC) Received: from us-smtp-delivery-199.mimecast.com (us-smtp-delivery-199.mimecast.com [63.128.21.199]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 497525FC72 for ; Tue, 15 Aug 2017 05:00:31 +0000 (UTC) Received: from mx01.five9.com (mx01.five9.com [198.105.204.2]) (Using TLS) by us-smtp-1.mimecast.com with ESMTP id us-mta-132-5gR3cWtVNK2E7-vl7xDBbg-13; Tue, 15 Aug 2017 01:00:28 -0400 Received: from MB01.five9.com (10.192.8.141) by mx01.five9.com (10.7.15.111) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 14 Aug 2017 21:59:57 -0700 Received: from MB03.five9.com ([169.254.6.89]) by mb01.five9.com ([169.254.1.106]) with mapi id 14.03.0248.002; Mon, 14 Aug 2017 22:00:09 -0700 From: Alexander Smirnov To: "user@flink.apache.org" Subject: Time zones problem Thread-Topic: Time zones problem Thread-Index: AQHTFYNfXpFA27rQLUOpSuGeZTX4dw== Date: Tue, 15 Aug 2017 05:00:10 +0000 Message-ID: Accept-Language: ru-RU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.3.170325 x-originating-ip: [10.7.8.112] MIME-Version: 1.0 X-MC-Unique: 5gR3cWtVNK2E7-vl7xDBbg-13 Content-Type: multipart/alternative; boundary="_000_D5B7CDE91A2DEasmirnovfive9com_" archived-at: Tue, 15 Aug 2017 05:00:45 -0000 --_000_D5B7CDE91A2DEasmirnovfive9com_ Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Hello everybody, I=92m exploring Flink options to build statistics engine for call center so= lution. One thing I=92m not sure how to implement. Currently have the following jobs in the architecture. Job #1 =96 is for matching start and end events and calculate durations. Li= ke having call started and call ended events it is possible to calculate ho= w long was the call. Job #2 =96 is for aggregating precomputed values using multiple time window= s, like 1 hour, 1 day, 1 week. (can we define time windows run-time by the = way?). Also it joins control stream to care of subscription requests. Supervisors, who consume the statistics, are spread around the world and ca= n work in different time zones. So, having time window defined as 1 day results in different data for Europ= ean and American supervisors at exactly the same moment. I=92m not sure how to achieve that with Flink. What are the best practices to work with different time zones? Any hint is = appreciated. Thanks, Alex ________________________________ CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain conf= idential information of Five9 and/or its affiliated entities. Access by the= intended recipient only is authorized. Any liability arising from any part= y acting, or refraining from acting, on any information contained in this e= -mail is hereby excluded. If you are not the intended recipient, please not= ify the sender immediately, destroy the original transmission and its attac= hments 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= . --_000_D5B7CDE91A2DEasmirnovfive9com_ Content-Type: text/html; charset=WINDOWS-1252 Content-ID: <4B93B1D9D8D87C4DBF2DEAB82AE11A57@five9.com> Content-Transfer-Encoding: quoted-printable
Hello everybody,

I=92m exploring Flink options to build statistics engine for call cent= er solution.
One thing I=92m not sure how to implement. 

Currently have the following jobs in the architecture.

Job #1 =96 is for matching start and end events and calculate duration= s. Like having call started and call ended events it is possible to calcula= te how long was the call.
Job #2 =96 is for aggregating precomputed values using multiple time w= indows, like 1 hour, 1 day, 1 week. (can we define time windows run-time by= the way?). Also it joins control stream to care of subscription requests.<= /div>

Supervisors, who consume the statistics, are spread around the world a= nd can work in different time zones. 
So, having time window defined as 1 day results in different data for = European and American supervisors at exactly the same moment.

I=92m not sure how to achieve that with Flink.
What are the best practices to work with different time zones? Any hin= t is appreciated.

Thanks,
Alex



CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain conf= idential information of Five9 and/or its affiliated entities. Access by the= intended recipient only is authorized. Any liability arising from any part= y 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 conte= nts 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.
--_000_D5B7CDE91A2DEasmirnovfive9com_--