Mailing-List: contact user-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@flink.apache.org
MIME-Version: 1.0
From: Vinay Patil <vinay18.patil@gmail.com>
Date: Sun, 2 Oct 2016 22:21:34 -0500
Message-ID: <CAMpYU5QKCTqeGkE8qkSFBn4Q-rdqLmox7i0rWb=7H-kH9+U65w@mail.gmail.com>
Subject: Regarding Late Elements
To: user@flink.apache.org
Content-Type: multipart/alternative; boundary=001a1141c956ef88b6053ded70f6
archived-at: Mon, 03 Oct 2016 03:21:45 -0000

--001a1141c956ef88b6053ded70f6
Content-Type: text/plain; charset=UTF-8

Hi Guys,

Just wanted to get an idea on Why Flink decided to completely discard late
elements in the latest version ?, this was not the case in 1.0.3


P.S In our case the data is critical so we cannot discard a single record
even if it is late, I have written a custom trigger (as suggested by
Aljoscha) to even accept late elements.


Regards,
Vinay Patil

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

<div dir=3D"ltr">Hi Guys,<div><br></div><div>Just wanted to get an idea on =
Why Flink decided to completely discard late elements in the latest version=
 ?, this was not the case in 1.0.3<br><br><br>P.S In our case the data is c=
ritical so we cannot discard a single record even if it is late, I have wri=
tten a custom trigger (as suggested by Aljoscha) to even accept late elemen=
ts.<br><br></div><div><br clear=3D"all"><div><div class=3D"gmail_signature"=
 data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr">=
<font color=3D"#000000">Regards,</font><div><font color=3D"#000000">Vinay P=
atil</font></div></div></div></div></div></div>
</div></div>

--001a1141c956ef88b6053ded70f6--