Re: What is the best way to load/add patterns dynamically (at runtime) with Flink?

Hi Sameer, I just replied to the earlier post, but I will copy it here: We also have the same requirement - we want to allow the user to change the matching patterns and have them take effect immediately. I'm wondering whether the proposed trigger DSL takes us one step closer:(I don't think it so

Re: What is the best way to load/add patterns dynamically (at runtime) with Flink?

We also have the same requirement - we want to allow the user to change the matching patterns and have them take effect immediately. I'm wondering whether the proposed trigger DSL takes us one step closer:(I don't think it solves the problem) or we have to dynamically generate Flink job JAR file

Re: more complex patterns for CEP (was: CEP two transitions to the same state)

Thanks, Till. I will wait for your response. - LF From: Till Rohrmann To: user@flink.apache.org; lg...@yahoo.com Sent: Tuesday, October 11, 2016 2:49 AM Subject: Re: more complex patterns for CEP (was: CEP two transitions to the same state) The timeline is hard to predict to be

Re: Listening to timed-out patterns in Flink CEP

>>FLINK-3320 (CEP "not" operator) does not address this because again, how >>would the "not match" be triggered if no event at all occurs? Good question. I'm not sure whether the following will work: This could be done by creating a CEP matching pattern that uses both of "notNext" (or "notFollow

Re: Listening to timed-out patterns in Flink CEP

The following is a better link: http://mail-archives.apache.org/mod_mbox/flink-user/201609.mbox/%3CCAC27z%3DOTtv7USYUm82bE43-DkoGfVC4UAWD6uQwwRgTsE5be8g%40mail.gmail.com%3E - LF   From: "lg...@yahoo.com" To: "user@flink.apache.org" Sent: Friday, October 7, 2016 3:36 PM Subject: Re

Re: more complex patterns for CEP (was: CEP two transitions to the same state)

hi Till, Thanks for the detailed response. I'm looking forward to seeing these features implemented in Flink. Can anyone provide timelines for the 3 tickets that you mentioned in your response?  - LF From: Till Rohrmann To: user@flink.apache.org Sent: Tuesday, September 20, 2016 7:13

Re: Listening to timed-out patterns in Flink CEP

Isn't the upcoming CEP negation (absence of an event) feature solve this issue? See this discussion thread:http://mail-archives.apache.org/mod_mbox/flink-user/201609.mbox/%3CCAC27z%3DOD%2BTq8twBw_1YKni5sWAU3g1S9WDpJw0DUwgiG9YX9Fg%40mail.gmail.com%3E  //  Atul From: Till Rohrmann To: user

Re: Regarding Late Elements

igger 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.] <[hidden email]> wrote: We have the same requirement - we cannot discard any data even if it arrives late.  - LF   From: Vinay Pat

Re: Regarding Late Elements

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

Re: more complex patterns for CEP - Negation (was: CEP two transitions to the same state)

Hi, We are also looking for negation (absence of an event) functionality in Flink CEP. Something like notFollowedBy/notNext that detects the following patterns will be great additions to Flink CEP (other CEP frameworks support negation):1. Occurrence of an event (that matches specific criteria