[
https://issues.apache.org/jira/browse/FLINK-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498112#comment-16498112
]
ASF GitHub Bot commented on FLINK-9476:
---------------------------------------
Github user Aitozi commented on a diff in the pull request:
https://github.com/apache/flink/pull/6104#discussion_r192428106
--- Diff: docs/dev/libs/cep.md ---
@@ -1524,7 +1524,52 @@ In `CEP` the order in which elements are processed
matters. To guarantee that el
To guarantee that elements across watermarks are processed in event-time
order, Flink's CEP library assumes
*correctness of the watermark*, and considers as *late* elements whose
timestamp is smaller than that of the last
-seen watermark. Late elements are not further processed.
+seen watermark. Late elements are not further processed. Also, you can
specify a sideOutput tag to collect the late elements come after the last seen
watermark, you can use it like this.
+
+<div class="codetabs" markdown="1">
+<div data-lang="java" markdown="1">
+
+{% highlight java %}
+PatternStream<Event> patternStream = CEP.pattern(input, pattern);
+
+OutputTag<String> lateDataOutputTag = new
OutputTag<String>("late-data""){};
+
+OutputTag<String> outputTag = new OutputTag<String>("side-output""){};
--- End diff --
removed
> Lost sideOutPut Late Elements in CEP Operator
> ---------------------------------------------
>
> Key: FLINK-9476
> URL: https://issues.apache.org/jira/browse/FLINK-9476
> Project: Flink
> Issue Type: Improvement
> Components: CEP
> Affects Versions: 1.4.2
> Reporter: aitozi
> Assignee: aitozi
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
