[
https://issues.apache.org/jira/browse/FLINK-8947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek closed FLINK-8947.
-----------------------------------
Resolution: Not A Problem
This is working as intended. The bounded extractor will only emit a higher
watermark when it "sees" new data. You can write a custom watermark assigner
derived from {{AssignerWithPeriodicWatermarks}} that also advances the
event-time/watermark when not seeing new data.
> Timeout handler issue
> ---------------------
>
> Key: FLINK-8947
> URL: https://issues.apache.org/jira/browse/FLINK-8947
> Project: Flink
> Issue Type: Bug
> Components: CEP
> Affects Versions: 1.4.2
> Reporter: dhiraj prajapati
> Priority: Critical
>
> The issue is same as FLINK-5753
> I am using Event time and have used watermark interval. Still, I have
> observed the timeout executes only after the next event
> 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
>
> My code snippet:
> DataStream<String> dataStream = env.socketTextStream("localhost", 1212);
> dataStream.getExecutionConfig().setAutoWatermarkInterval(100L);
> dataStream = dataStream.assignTimestampsAndWatermarks(new
> BoundedOutOfOrdernessTimestampExtractor<JSONObject>(
> Time.seconds(0)) {
> private static final long serialVersionUID = 4969170359023055566L;
> @Override
> public long extractTimestamp(JSONObject event) {
> return System.currentTimeMillis();
> }
> });
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
