Re: CEP timeout occurs even for a successful match when using followedBy

Glad to hear that Moiz! And thanks for helping us test out the library. Kostas > On May 2, 2017, at 12:34 PM, Moiz S Jinia wrote: > > Thanks! I downloaded and built 1.3-SNAPSHOT locally and was able to verify > that followedBy now works as I want. > > Moiz > > On Sat,

Re: CEP timeout occurs even for a successful match when using followedBy

Thanks! I downloaded and built 1.3-SNAPSHOT locally and was able to verify that followedBy now works as I want. Moiz On Sat, Apr 29, 2017 at 11:08 PM, Kostas Kloudas < k.klou...@data-artisans.com> wrote: > Hi Moiz, > > Here are the instructions on how to build Flink from source: > >

Re: CEP timeout occurs even for a successful match when using followedBy

Hi Moiz, Here are the instructions on how to build Flink from source: https://ci.apache.org/projects/flink/flink-docs-release-1.2/setup/building.html Kostas > On Apr 29, 2017, at 7:15 PM, Moiz S Jinia

Re: CEP timeout occurs even for a successful match when using followedBy

I meant maven dependencies that i can use by generating them from sources. On Sat, Apr 29, 2017 at 10:31 PM, Moiz S Jinia wrote: > Ok I'll try that. Its just that I'd rather use a stable version. > Are there any instructions for building binaries from latest sources? > >

Re: CEP timeout occurs even for a successful match when using followedBy

Ok I'll try that. Its just that I'd rather use a stable version. Are there any instructions for building binaries from latest sources? Moiz On Sat, Apr 29, 2017 at 10:09 PM, Kostas Kloudas < k.klou...@data-artisans.com> wrote: > Hi Moiz, > > The skip-till-next is a big change and backporting it

Re: CEP timeout occurs even for a successful match when using followedBy

Hi Moiz, The skip-till-next is a big change and backporting it does not seem feasible. Also this would require more general changes to the 1.2 to make it compatible with the previous 1.2 versions. If you want you can already use the 1.3 version by downloading the master branch and writing

Re: CEP timeout occurs even for a successful match when using followedBy

Oh ok thats a bit far off. Is there any chance of a backport of https://issues.apache.org/jira/browse/FLINK-6208 to the 1.2 branch? I require the SKIP_TILL_NEXT behaviour for a production use case that we want to use Flink for. Moiz On Sat, Apr 29, 2017 at 9:49 PM, Kostas Kloudas

Re: CEP timeout occurs even for a successful match when using followedBy

The 1.3 is scheduled for the beginning of June. Cheers, Kostas > On Apr 29, 2017, at 6:16 PM, Moiz S Jinia wrote: > > Thanks Dawid! > Yes thats what i was expecting. I'll give it a try. > > When do you expect 1.3.0 stable to be out? > > Moiz > > On Sat, Apr 29, 2017

Re: CEP timeout occurs even for a successful match when using followedBy

Thanks Dawid! Yes thats what i was expecting. I'll give it a try. When do you expect 1.3.0 stable to be out? Moiz On Sat, Apr 29, 2017 at 9:20 PM, Dawid Wysakowicz < wysakowicz.da...@gmail.com> wrote: > Hi, > > This is an expected behaviour. After the "ar" event there still may occur > other

Re: CEP timeout occurs even for a successful match when using followedBy

Hi, This is an expected behaviour. After the "ar" event there still may occur other "ar" event that will also trigger a match. To be more generic in all versions prior to 1.3.0 there are two different consuming strategies: - STRICT (the next operator) - that accepts only if the event occurs

CEP timeout occurs even for a successful match when using followedBy

When using "next", this pattern works fine for the both a match as well as a timeout: Pattern pattern = Pattern.begin("start") .where(evt -> evt.value.equals("ni")) .next("last").where(evt -> evt.value.equals("ar")).within(Time.seconds(5)); 1. "ni" then "ar" within