Great to hear that things are now working :-)
On Sun, Jun 11, 2017 at 11:19 PM, David Koch wrote:
> Hello,
>
> It's been a while and I have never replied on the list. In fact, the fix
> committed by Till does work. Thanks!
>
> On Tue, Apr 25, 2017 at 9:37 AM, Moiz Jinia wrote:
>
>> Hey David,
>
Hello,
It's been a while and I have never replied on the list. In fact, the fix
committed by Till does work. Thanks!
On Tue, Apr 25, 2017 at 9:37 AM, Moiz Jinia wrote:
> Hey David,
> Did that work for you? If yes could you share an example. I have a similar
> use case - need to get notified of
Hey David,
Did that work for you? If yes could you share an example. I have a similar
use case - need to get notified of an event NOT occurring within a specified
time window.
Thanks much!
Moiz
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.co
;> autoWatermarkInterval
>>>>>>>> (or less to be conservative).
>>>>>>>>
>>>>>>>> You can check if the watermark has changed since the arrival of the
>>>>>>>> last event and if not increment it in the getCurrentWatermark() method.
>>>>>>>> Othe
gt;>> till.rohrm...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hi David,
>>>>>>>>
>>>>>>>> the problem is still that there is no corresponding watermark
>>>>>>>> saying that 4 seconds ha
t;>> periodically emitted but the same watermark will be emitted until a new
>>>>>>> element arrives which will reset the watermark. Thus, the system can
>>>>>>> never
>>>>>>> know until this watermark is seen whether there will be an
;>>>>>>
>>>>>>> ----------
>>>>>>> *From:* David Koch
>>>>>>> *To:* user@flink.apache.org; lg...@yahoo.com
>>>>>>> *Sent:* Sunday, October 9, 2016 5:51 AM
>>>>>>>
>>>&g
t;>>> "not" operator) does not address this because again, how would the "not
>>>>>> match" be triggered if no event at all occurs?
>>>>>>
>>>>>> Good question.
>>>>>>
>>>&
gt;>>
>>>>> 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 "notFollowedB
EP matching pattern that uses both of
>>>> "notNext" (or "notFollowedBy") and "within" constructs. Something like
>>>> this:
>>>>
>>>> Pattern pattern = Pattern.begin("first")
>>>> .no
constructs. Something like
>>>> this:
>>>>
>>>> Pattern pattern = Pattern.begin("first")
>>>> .notNext("second")
>>>> .within(Time.seconds(3));
>>>>
>>>> I'm hoping Flink CEP experts
n(Time.seconds(3));
>>>
>>> I'm hoping Flink CEP experts (Till?) will comment on this.
>>>
>>> Note: I have requested these negation patterns to be implemented in
>>> Flink CEP, but notNext/notFollowedBy are not yet implemented in Flink..
>>>
Note: I have requested these negation patterns to be implemented in Flink
>> CEP, but notNext/notFollowedBy are not yet implemented in Flink..
>>
>>
>> - LF
>>
>>
>>
>>
>> --
>> *From:* David Koch
>> *To:
>
>
> - LF
>
>
>
>
> ----------
> *From:* David Koch
> *To:* user@flink.apache.org; lg...@yahoo.com
> *Sent:* Sunday, October 9, 2016 5:51 AM
>
> *Subject:* Re: Listening to timed-out patterns in Flink CEP
>
> Hello,
>
> Thank
Note: I have requested these negation patterns to be implemented in Flink CEP,
but notNext/notFollowedBy are not yet implemented in Flink..
- LF
From: David Koch
To: user@flink.apache.org; lg...@yahoo.com
Sent: Sunday, October 9, 2016 5:51 AM
Subject: Re: Listening to timed-out pa
-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: Listening to timed-out patterns in Flink CEP
>
&
016 3:36 PM
Subject: 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_1YKni5sWAU3g1S9WDpJw0DUwg
To: user@flink.apache.org
Sent: Friday, October 7, 2016 12:58 AM
Subject: Re: Listening to timed-out patterns in Flink CEP
Hi David,
in case of event time, the timeout will be detected when the first watermark
exceeding the timeout value is received. Thus, it depends a little bit how you
gen
Hi David,
in case of event time, the timeout will be detected when the first
watermark exceeding the timeout value is received. Thus, it depends a
little bit how you generate watermarks (e.g. periodically, watermark per
event).
In case of processing time, the time is only updated whenever a new e
19 matches
Mail list logo