flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kostas Kloudas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5753) CEP timeout handler.
Date Sat, 13 May 2017 11:47:04 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009284#comment-16009284

Kostas Kloudas commented on FLINK-5753:

Hi [~jurijuri].

Did you configure your watermark interval and specify a watermark generator and timestamp
{{env.getConfig().setAutoWatermarkInterval(100L);}} (interval)
{{inputStream.assignTimestampsAndWatermarks( TIMESTAMP_ASSIGNER_AND_WATERMARK_GENERATOR)}}
(wm generator)

Without these, there are no watermarks flowing in your system so the system time does not
advance, but only element timestamps trigger 
the computation.

> CEP timeout handler.
> --------------------
>                 Key: FLINK-5753
>                 URL: https://issues.apache.org/jira/browse/FLINK-5753
>             Project: Flink
>          Issue Type: Bug
>          Components: CEP
>    Affects Versions: 1.1.2
>            Reporter: MichaƂ Jurkiewicz
>            Assignee: Kostas Kloudas
> I configured the following flink job in my environment:
> {code}
> Pattern<Event, ?> patternCommandStarted = Pattern.<Event> begin("event-accepted").subtype(Event.class)
> .where(e -> {event accepted where statement}).next("second-event-started").subtype(Event.class)
> .where(e -> {event started where statement}))
> .within(Time.seconds(30));
> DataStream<Either<Event, Event>> events = CEP
>   .pattern(eventsStream.keyBy(e -> e.getEventProperties().get("deviceCode")), patternCommandStarted)
>   .select(eventSelector, eventSelector);
> static class EventSelector implements PatternSelectFunction<Event, Event>, PatternTimeoutFunction<Event,
Event> {}
> {code}
> The problem that I have is related to timeout handling. I observed that: 
> if: first event appears, second event not appear in the stream  
> and *no new events appear in a stream*, timeout handler is not executed.
> Expected result: timeout handler should be executed in case if there are no new events
in a stream

This message was sent by Atlassian JIRA

View raw message