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 82F0A200BD0 for ; Wed, 30 Nov 2016 19:08:59 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 819B7160B28; Wed, 30 Nov 2016 18:08:59 +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 A56FE160B06 for ; Wed, 30 Nov 2016 19:08:58 +0100 (CET) Received: (qmail 40129 invoked by uid 500); 30 Nov 2016 18:08:52 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flink.apache.org Delivered-To: mailing list user@flink.apache.org Received: (qmail 40119 invoked by uid 99); 30 Nov 2016 18:08:52 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Nov 2016 18:08:52 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 45AC418009D for ; Wed, 30 Nov 2016 18:08:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.38 X-Spam-Level: ** X-Spam-Status: No, score=2.38 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=olacabs.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id nUoem8E5gOy5 for ; Wed, 30 Nov 2016 18:08:50 +0000 (UTC) Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com [209.85.220.177]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id E12EC5FCA2 for ; Wed, 30 Nov 2016 18:08:49 +0000 (UTC) Received: by mail-qk0-f177.google.com with SMTP id n204so218273248qke.2 for ; Wed, 30 Nov 2016 10:08:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=olacabs.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=3GB7aQ+v6/LWbn/cBSo0yaEPWJEFq761ttO51uNoJL0=; b=d3vrmD7+ZmTdov6eCb1UBnOsGJOKjQTZ7I2EMUEgRNkUycr1ycLL2spa6vwt6DfYIJ KDvvDsSYLVLGdUSR0qiR1EUiTh9vF/UGjwpH1Rcxlvn3BD3ww5ARbIShJLm4peUz30rl POOE993vZofTP6GRpC13AwZiGrRmo5383auM6vaAxlgNr0k/BCKI9VrKFM0+ZhVzndYV 1eVwA4PXP8r+7Y97o4Uc3LbfkeUsm5+dT6q4x8CIZpttBg2d08NGbMM2EC6jYlgBCSWK oxHsg3DSIHUiEJy2Fwcmy16rQKQ+/tcwaq0qXpowDrlkCXI/jglNqeuQlsMIJy8NRpfQ beWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=3GB7aQ+v6/LWbn/cBSo0yaEPWJEFq761ttO51uNoJL0=; b=AZKgNTFptQcbAlB+HP0r/ULyEFuJiXnNdIujsd/r6x4+MVoTPU17XIiXOArE9eCXY1 EkMdzjPgXGEwweUqVAIDpjUETraRaxYA+8t49Y0fa5s9Q9eM/+OUzqUPfFgzc9CpmG1d rlT5+NHleCpjXpmi6xpDVq/w+QuzH9t32KU2ZTxEOq6jo6H6O1Hrw/dNl4LLfgVM6EyQ 6jeQ4xIjCWbz1z1d4X5E1YCoIthsV8PsTlrWHilLV5coK1+a+J4bX38CHZFSub49tbZL 7ms2DaPZfuq7lvW7mwBnJmZFQVPXzjJOLceLs2bGaLIkUTCTMPxUqSmNYM90Z4vV1wIX XigA== X-Gm-Message-State: AKaTC00OUOmdEmy5FbQtrF22j8J1hxH2NVmQJMKmMznRCD6ldY4CauaKEYUTMJ6nMO0FpKS1KJzWOnSaOZadfDvn X-Received: by 10.55.144.6 with SMTP id s6mr30289712qkd.266.1480529326829; Wed, 30 Nov 2016 10:08:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.150.54 with HTTP; Wed, 30 Nov 2016 10:08:06 -0800 (PST) In-Reply-To: References: From: Janardhan Reddy Date: Wed, 30 Nov 2016 23:38:06 +0530 Message-ID: Subject: Re: Query regarding tumbling event time windows with ingestion time To: user@flink.apache.org Content-Type: multipart/alternative; boundary=94eb2c0859689b19a00542889883 archived-at: Wed, 30 Nov 2016 18:08:59 -0000 --94eb2c0859689b19a00542889883 Content-Type: text/plain; charset=UTF-8 That makes it clear. Thanks On Wed, Nov 30, 2016 at 10:15 PM, Kostas Kloudas < k.kloudas@data-artisans.com> wrote: > Hello, > > If you have events: > > A@10m, B@14m, Watermark@15m > C@16m D@25m, Watermark@30m > > then the result will be: > > [A,B]@14.59 > [C,D]@29.59 > > This means that for the next windowing, you will have the elements > [A,B]@14.59 and [C,D]@29.59 > to window in windows of 5min. > > Given that they are 15min apart, this means that you will have: > > [A,B]@14.59 in one window and [C,D]@29.59 > > This is what I meant by at most one element per window, because window 0 > to 5 min, 5 to 10 and > 15 to 20 and 20 to 25 will be empty. > > Does this make it clearer? > > Kostas > > On Nov 30, 2016, at 11:48 AM, Janardhan Reddy > wrote: > > HI > i didn't get it , can you please clarify with an example in case each of > operation A and B emit multiple elements. > > On Wed, Nov 30, 2016 at 3:34 PM, Kostas Kloudas < > k.kloudas@data-artisans.com> wrote: > >> Hi Janardhan, >> >> After the first windowing operation, the timestamp of the emitted element >> for each window >> will be the (endOfWindow - 1). So in your case, in the second windowing >> operation (window by 5) >> there will be at most one element per window. >> >> I hope this answers your question. >> >> Kostas >> >> > On Nov 29, 2016, at 7:25 PM, Janardhan Reddy < >> janardhan.reddy@olacabs.com> wrote: >> > >> > Hi, >> > >> > Suppose we have a stream like this. >> > >> > someStream.timeWindow(Time.minutes(15)).apply { >> > operation A >> > >> > }.keyby("....").window(TumblingEventTimeWindows.ofseconds(5)).apply { >> > >> > operation B >> > >> > }.keyby("....").window(TumblingEventTimeWindows.ofseconds(5)).apply { >> > >> > operation C >> > >> > } >> > >> > Say operation A emits some elements => it would be emitted every 15 >> minutes. >> > >> > How would be the window behaviour of where operation B takes place if >> operation A takes more than 5 seconds with ingestion Time characteristic. >> Similarly how would windows behave near operation C if operation B takes >> more than 5 seconds. >> > >> > >> > Thanks >> > Janardhan >> >> > > --94eb2c0859689b19a00542889883 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That makes it clear.

Thanks
=

On Wed, Nov 30, 2= 016 at 10:15 PM, Kostas Kloudas <k.kloudas@data-artisans.com= > wrote:
Hello,

If you have events:

<= div>A@10m, B@14m, Watermark@15m=C2=A0
C@16m D@25m, Watermark@30m<= /div>

then the result will be:

= [A,B]@14.59
[C,D]@29.59

This means that = for the next windowing, you will have the elements [A,B]@14.59 and [C,D]@29= .59
to window in windows of 5min.=C2=A0

= Given that they are 15min apart, this means that you will have:
<= br>
[A,B]@14.59 in one window and [C,D]@29.59

This is what I meant by at most one element per window, because windo= w 0 to 5 min, 5 to 10 and=C2=A0
15 to 20 and 20 to 25 will be emp= ty.

Does this make it clearer?

Kostas

On Nov 30, 2016, at 11:48 AM, Janardhan Reddy <janardhan.reddy@olacabs.com= > wrote:

HI
i didn't get it , can you please cl= arify with an example in case each of operation A and B emit multiple eleme= nts.

O= n Wed, Nov 30, 2016 at 3:34 PM, Kostas Kloudas <k.kloudas@data-a= rtisans.com> wrote:
Hi Jana= rdhan,

After the first windowing operation, the timestamp of the emitted element f= or each window
will be the (endOfWindow - 1). So in your case, in the second windowing ope= ration (window by 5)
there will be at most one element per window.

I hope this answers your question.

Kostas

> On Nov 29, 2016, at 7:25 PM, Janardhan Reddy <janardhan.reddy@olacabs.com= > wrote:
>
> Hi,
>
> Suppose we have a stream like this.
>
> someStream.timeWindow(Time.minutes(15)).apply {
> operation A
>
> }.keyby("....").window(TumblingEventTimeWindows.ofsecon= ds(5)).apply {
>
> operation B
>
> }.keyby("....").window(TumblingEventTimeWindows.ofsecon= ds(5)).apply {
>
> operation C
>
> }
>
> Say operation A emits some elements =3D> it would be emitted every = 15 minutes.
>
> How would be the window behaviour of where operation B takes place if = operation A takes more than 5 seconds with ingestion Time characteristic.= =C2=A0 Similarly how would windows behave near operation C if operation B t= akes more than 5 seconds.
>
>
> Thanks
> Janardhan




--94eb2c0859689b19a00542889883--