Re: Regarding Late Elements

2016-10-04 Thread vinay patil
e-flink-user-mailing-list-archive.2336050.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers

Re: Regarding Late Elements

2016-10-04 Thread Kostas Kloudas
pace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > View this message in context: Re: Regarding Late Elements > <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Regarding-Late-Elements-tp9284p9331.html> > Sent from the Apache Flink User Mailing List archive. mailing list archive > <http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/> at > Nabble.com.

Re: Regarding Late Elements

2016-10-04 Thread vinay patil
Hi Kostas, Yes you are right , I am always doing FIRE_AND_PURGE , if we don't do this and only use FIRE , the window function will get the elements in incremental fashion (1, 2,3..so on) I had observed this while testing. Can you please explain me the importance of canMerge and onMerge functions

Re: Regarding Late Elements

2016-10-04 Thread Kostas Kloudas
Hi Vinay, By setting the allowed_lateness to LongMax you are ok. Sorry I forgot that this was the default value. Just a note (although you have it right in your code), in this case you should always FIRE_AND_PURGE and not just FIRE. In other case your state will keep growing as it is never ga

Re: Regarding Late Elements

2016-10-04 Thread vinay patil
am with only these elements. >> >> Thanks, >> Kostas >> >> On Oct 3, 2016, at 5:28 PM, [hidden email] >> <http://user/SendEmail.jtp?type=node&node=9307&i=0> wrote: >> >> Not yet. >> I'm hoping a Flink export on this mailing list wil

Re: Regarding Late Elements

2016-10-04 Thread Kostas Kloudas
=9307&i=0> wrote: >> >> Not yet. >> I'm hoping a Flink export on this mailing list will reply. >> >> >> - LF >> >> >> >> From: vinay patil <[hidden email] >> <http://user/SendEmail.jtp?type=node&node=9307&am

Re: Regarding Late Elements

2016-10-04 Thread vinay patil
-- > *From:* vinay patil <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=9307&i=1>> > *To:* [hidden email] <http:///user/SendEmail.jtp?type=node&node=9307&i=2> > *Sent:* Monday, October 3, 2016 8:09 AM > *Subject:* Re: Regarding

Re: Regarding Late Elements

2016-10-04 Thread Kostas Kloudas
et. > I'm hoping a Flink export on this mailing list will reply. > > > - LF > > > > From: vinay patil > To: user@flink.apache.org > Sent: Monday, October 3, 2016 8:09 AM > Subject: Re: Regarding Late Elements > > Hi LF, > > So did you manage to g

Re: Regarding Late Elements

2016-10-03 Thread lgfmt
Not yet. I'm hoping a Flink export on this mailing list will reply. - LF From: vinay patil To: user@flink.apache.org Sent: Monday, October 3, 2016 8:09 AM Subject: Re: Regarding Late Elements Hi LF, So did you manage to get the workaround for it ? I am using a Custom Tr

Re: Regarding Late Elements

2016-10-03 Thread vinay patil
Hi LF, So did you manage to get the workaround for it ? I am using a Custom Trigger which is similar to 1.0.3 with few changes Regards, Vinay Patil On Mon, Oct 3, 2016 at 10:02 AM, lgfmt [via Apache Flink User Mailing List archive.] wrote: > We have the same requirement - we cannot discard an

Re: Regarding Late Elements

2016-10-03 Thread lgfmt
We have the same requirement - we cannot discard any data even if it arrives late.  - LF   From: Vinay Patil To: user@flink.apache.org Sent: Sunday, October 2, 2016 8:21 PM Subject: Regarding Late Elements Hi Guys, Just wanted to get an idea on Why Flink decided to completely dis