Thanks, I follow your suggestion and it works as we expected.
Best,
Sendoh
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/How-to-let-1-1-3-not-drop-late-events-as-verion-1-0-3-does-tp10349p10510.html
Sent from the Apache Flink User Mailing
t;>
> >> http://apache-flink-user-mailing-list-archive.2336050.
> n4.nabble.com/How-to-let-1-1-3-not-drop-late-events-as-
> verion-1-0-3-does-tp10349.html
> >> To start a new topic under Apache Flink User Mailing List archive.,
> email
> >> [hidden email]
> &g
ail, your message will be added to the
> discussion
> >> below:
> >>
> >>
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/How-to-let-1-1-3-not-drop-late-events-as-verion-1-0-3-does-tp10349.html
> >> To start a new topic under Apache
; To start a new topic under Apache Flink User Mailing List archive.,
> email
> >> [hidden email]
> >> To unsubscribe from Apache Flink User Mailing List archive., click
> here.
> >> NAML
> >
> >
> >
> >
&g
pache Flink User Mailing List archive., email
>> [hidden email]
>> To unsubscribe from Apache Flink User Mailing List archive., click here.
>> NAML
>
>
>
>
> View this message in context: Re: How to let 1.1.3 not drop late events as
> verion 1.0.3 does
>
> Sent from the Apache Flink User Mailing List archive. mailing list archive
> at Nabble.com.
Hi Sendoh,
I have used the Custom Trigger which is same as 1.0.3 EventTimeTrigger, and
kept the allowedLateness value to Long.MAX_VALUE.
Because of this change the late elements are not discarded and become
single element windows
Regards,
Vinay Patil
On Mon, Nov 28, 2016 at 5:54 PM, Sendoh [via
Hi Flink users,
Can I ask how to avoid default allowLateness(0) ? so that late events
becomes single-element windows as 1.0.3 version acts?
Best,
Sendoh
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/How-to-let-1-1-3-not-drop-late-events
