You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "aitozi (JIRA)" <ji...@apache.org> on 2018/06/06 02:52:00 UTC
[jira] [Assigned] (FLINK-9533) CEP cant deal with the known
outOfOrder config with event time
[ https://issues.apache.org/jira/browse/FLINK-9533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
aitozi reassigned FLINK-9533:
-----------------------------
Assignee: aitozi
Affects Version/s: 1.4.2
Description:
As described in the [stackoverflow|[https://stackoverflow.com/questions/48694927/flink-cep-pattern-does-not-match-for-first-events-after-starting-job-and-always]|https://stackoverflow.com/questions/48694927/flink-cep-pattern-does-not-match-for-first-events-after-starting-job-and-always],]
when set the watermark generate with the maxOutOfOrder, it will run into problem when we extract events from bufferEvent to process, should fix it.
Component/s: CEP
Summary: CEP cant deal with the known outOfOrder config with event time (was: CEP)
> CEP cant deal with the known outOfOrder config with event time
> --------------------------------------------------------------
>
> Key: FLINK-9533
> URL: https://issues.apache.org/jira/browse/FLINK-9533
> Project: Flink
> Issue Type: Bug
> Components: CEP
> Affects Versions: 1.4.2
> Reporter: aitozi
> Assignee: aitozi
> Priority: Major
>
> As described in the [stackoverflow|[https://stackoverflow.com/questions/48694927/flink-cep-pattern-does-not-match-for-first-events-after-starting-job-and-always]|https://stackoverflow.com/questions/48694927/flink-cep-pattern-does-not-match-for-first-events-after-starting-job-and-always],]
> when set the watermark generate with the maxOutOfOrder, it will run into problem when we extract events from bufferEvent to process, should fix it.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)