Return-Path: <user-return-10011-archive-asf-public=cust-asf.ponee.io@flink.apache.org>
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 8EF8E200BBF
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Mon, 14 Nov 2016 15:29:27 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 8DAB2160B06; Mon, 14 Nov 2016 14:29:27 +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 D6902160B05
	for <archive-asf-public@cust-asf.ponee.io>; Mon, 14 Nov 2016 15:29:26 +0100 (CET)
Received: (qmail 44079 invoked by uid 500); 14 Nov 2016 14:29:25 -0000
Mailing-List: contact user-help@flink.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@flink.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@flink.apache.org>
List-Post: <mailto:user@flink.apache.org>
List-Id: <user.flink.apache.org>
Reply-To: user@flink.apache.org
Delivered-To: mailing list user@flink.apache.org
Received: (qmail 44070 invoked by uid 99); 14 Nov 2016 14:29:25 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Nov 2016 14:29:25 +0000
Received: from mail-it0-f49.google.com (mail-it0-f49.google.com [209.85.214.49])
	by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 97AFE1A0617
	for <user@flink.apache.org>; Mon, 14 Nov 2016 14:29:25 +0000 (UTC)
Received: by mail-it0-f49.google.com with SMTP id q124so120959886itd.1
        for <user@flink.apache.org>; Mon, 14 Nov 2016 06:29:25 -0800 (PST)
X-Gm-Message-State: ABUngvdBtyNTht7+xfYd7HLDRc4iOIG/F38pYCc+RbOxMJ8+g4F9eMVhVeElcgye+fZ4h8taZFG92PjzReH8ww==
X-Received: by 10.107.197.1 with SMTP id v1mr6547116iof.119.1479133764746;
 Mon, 14 Nov 2016 06:29:24 -0800 (PST)
MIME-Version: 1.0
References: <CAKZehoUhXB_X7dWT7pAOjLB7k6pK-aPB_OhMGVZ7FbL9YMDhJA@mail.gmail.com>
 <etPan.58297d4a.1940fee6.143fc@apache.org>
In-Reply-To: <etPan.58297d4a.1940fee6.143fc@apache.org>
From: Aljoscha Krettek <aljoscha@apache.org>
Date: Mon, 14 Nov 2016 14:29:14 +0000
X-Gmail-Original-Message-ID: <CANMXwW2oAK+q_E=fx8wtstvnroS+doXiiWugvMWeBu75iH4EsQ@mail.gmail.com>
Message-ID: <CANMXwW2oAK+q_E=fx8wtstvnroS+doXiiWugvMWeBu75iH4EsQ@mail.gmail.com>
Subject: Re: Order by which windows are processed on event time
To: Ufuk Celebi <uce@apache.org>, Saiph Kappa <saiph.kappa@gmail.com>, user@flink.apache.org
Content-Type: multipart/alternative; boundary=94eb2c18a43c9f9d2a054143aad6
archived-at: Mon, 14 Nov 2016 14:29:27 -0000

--94eb2c18a43c9f9d2a054143aad6
Content-Type: text/plain; charset=UTF-8

Hi,
event-time windows are being processed in the order of their end timestamp.
If several windows have the same end timestamp then no ordering across
those windows is guaranteed.

Cheers,
Aljoscha

On Mon, 14 Nov 2016 at 10:01 Ufuk Celebi <uce@apache.org> wrote:

> I think there are no ordering guarantees for this. @Aljoscha: is this
> correct?
>
>
> On 11 November 2016 at 19:57:43, Saiph Kappa (saiph.kappa@gmail.com)
> wrote:
> > Hi,
> >
> > I have a streaming application based on event time. When I issue a
> > watermark that will close more than 1 window (and trigger their
> > processment), I can see that windows are computed sequentially (at least
> > using local machine) and that the computing order is not defined. Can I
> > change this behavior to make it compute from the oldest to the newest
> > window? Where in the flink code can I find this that handles the
> scheduling
> > of window processment?
> >
> > Thank you.
> >
>
>

--94eb2c18a43c9f9d2a054143aad6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div>event-time windows are being processed in the orde=
r of their end timestamp. If several windows have the same end timestamp th=
en no ordering across those windows is guaranteed.</div><div><br></div><div=
>Cheers,</div><div>Aljoscha</div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr">On Mon, 14 Nov 2016 at 10:01 Ufuk Celebi &lt;<a href=3D"mailto:=
uce@apache.org">uce@apache.org</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">I think there are no ordering guarantees for this. @Aljoscha: is=
 this correct?<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
On 11 November 2016 at 19:57:43, Saiph Kappa (<a href=3D"mailto:saiph.kappa=
@gmail.com" class=3D"gmail_msg" target=3D"_blank">saiph.kappa@gmail.com</a>=
) wrote:<br class=3D"gmail_msg">
&gt; Hi,<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; I have a streaming application based on event time. When I issue a<br =
class=3D"gmail_msg">
&gt; watermark that will close more than 1 window (and trigger their<br cla=
ss=3D"gmail_msg">
&gt; processment), I can see that windows are computed sequentially (at lea=
st<br class=3D"gmail_msg">
&gt; using local machine) and that the computing order is not defined. Can =
I<br class=3D"gmail_msg">
&gt; change this behavior to make it compute from the oldest to the newest<=
br class=3D"gmail_msg">
&gt; window? Where in the flink code can I find this that handles the sched=
uling<br class=3D"gmail_msg">
&gt; of window processment?<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
&gt; Thank you.<br class=3D"gmail_msg">
&gt;<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
</blockquote></div>

--94eb2c18a43c9f9d2a054143aad6--