[ https://issues.apache.org/jira/browse/FLINK-9533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
aitozi updated FLINK-9533: -------------------------- Description: As described in the [link title|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. was: 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. > 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 [link > title|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)