Hi Rafi, Currently this is unfortunately not supported out of the box. To support this, we need 2 features with one having to be added in Flink itself, and the other to the CEP library.
The first one is broadcast state and the ability to connect keyed and non-keyed streams. This one is to be added to Flink itself and the good news are that this feature is scheduled to be added to Flink 1.5. The second feature is to modify the CEP operator so that it can support multiple patterns and match incoming events against all of them. For this I have no clear deadline in my mind, but given that there are more and more people asking for it, I think it is going to be added soon. Thanks for raising the issue in the mailing list, Kostas > On Dec 27, 2017, at 2:44 PM, Ufuk Celebi <u...@apache.org> wrote: > > Hey Rafi, > > this is indeed a very nice feature to have. :-) I'm afraid that this > is currently hard to do manually with CEP. Let me pull in Dawid and > Klou (cc'd) who have worked a lot on CEP. They can probably update you > on the plan for FLINK-7129. > > Best, > > Ufuk > > > On Tue, Dec 26, 2017 at 8:47 PM, Shivam Sharma <28shivamsha...@gmail.com> > wrote: >> Hi Rafi, >> >> Even I also wanted this facility from Flink Core. But I think this is >> already solved by Uber on Flink. >> >> https://eng.uber.com/athenax/ >> >> Best >> >> On Tue, Dec 26, 2017 at 6:21 PM, Rafi Aroch <raf...@walkme.com> wrote: >> >>> Hi, >>> >>> I'm Rafi, Data Architect at WalkMe. >>> >>> Our Mobile platform generates events coming from the end-users mobile >>> device for different actions that the user does. >>> >>> The use case I wanted to implement using Flink CEP is as follows: >>> >>> We would like to expose a UI where we could define a set of rules. Rules >>> can be statefull, like: >>> >>> User did X 4 times in the last hour >>> AND >>> User did Y and then did Z in a session >>> AND >>> User average session duration is > 60 seconds >>> >>> As the set of rules are met, we would like to trigger an action. Like a >>> REST call, fire event, etc. >>> >>> This sounds like a good fit for Flink CEP, except that currently, I >>> understand that CEP patterns have to be "hard-coded" in my jobs code in >>> order to build the graph. >>> This set of rules may change many times a day. So re-deploying a Flink job >>> is not an option (or is it?). >>> >>> I found this ticket: https://issues.apache.org/jira/browse/FLINK-7129 and >>> was hoping you plan to add this feature soon :) >>> >>> This would make a powerful feature and open up many interesting use-cases. >>> >>> Meanwhile, can you suggest a way of implementing this use-case? >>> >>> Hope this makes sense. >>> Would love to hear your thoughts. >>> >>> Thanks, >>> Rafi >>> >> >> >> >> -- >> Shivam Sharma >> Data Engineer @ Goibibo >> Indian Institute Of Information Technology, Design and Manufacturing >> Jabalpur >> Mobile No- (+91) 8882114744 >> Email:- 28shivamsha...@gmail.com >> LinkedIn:-*https://www.linkedin.com/in/28shivamsharma >> <https://www.linkedin.com/in/28shivamsharma>*
