[
https://issues.apache.org/jira/browse/FLINK-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16039148#comment-16039148
]
ASF GitHub Bot commented on FLINK-6198:
---------------------------------------
Github user tzulitai commented on a diff in the pull request:
https://github.com/apache/flink/pull/4041#discussion_r120403427
--- Diff: docs/dev/libs/cep.md ---
@@ -1155,5 +1199,9 @@ The changes required are:
implementing the `FilterFunction` interface.
2. Change your functions provided as arguments to the `select(...)` and
`flatSelect(...)` methods to expect a list of
-events associated with each state (`List` in `Java`, `Iterable` in
`Scala`). This is because with the addition of
-the looping states, multiple input events can much a single (looping)
state.
\ No newline at end of file
+events associated with each pattern (`List` in `Java`, `Iterable` in
`Scala`). This is because with the addition of
+the looping patterns, multiple input events can match a single (looping)
pattern.
+
+3. The `followedBy()` in Flink 1.1 and 1.2 implied `non-deterministic
relaxed contiguity` (see
--- End diff --
Looks good! 😄
> Update the documentation of the CEP library to include all the new features.
> ----------------------------------------------------------------------------
>
> Key: FLINK-6198
> URL: https://issues.apache.org/jira/browse/FLINK-6198
> Project: Flink
> Issue Type: Sub-task
> Components: CEP
> Affects Versions: 1.3.0
> Reporter: Kostas Kloudas
> Assignee: Kostas Kloudas
> Priority: Critical
> Fix For: 1.3.0
>
>
> New features to include:
> * Iterative Functions
> * Quantifiers
> * Time handling
> * Migration from FilterFunction to IterativeCondition
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
