[
https://issues.apache.org/jira/browse/FLINK-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352616#comment-15352616
]
ASF GitHub Bot commented on FLINK-3319:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/2171#discussion_r68719946
--- Diff:
flink-libraries/flink-cep/src/test/java/org/apache/flink/cep/CEPITCase.java ---
@@ -424,87 +423,71 @@ public Integer select(Map<String, Integer> pattern)
throws Exception {
env.execute();
}
+ /**
+ * Checks that a certain event sequence is recognized with an OR filter
+ * @throws Exception
+ */
@Test
- public void testTimeoutHandling() throws Exception {
--- End diff --
Why do you remove the `testTimeoutHandling` test?
> Add or operator to CEP's pattern API
> ------------------------------------
>
> Key: FLINK-3319
> URL: https://issues.apache.org/jira/browse/FLINK-3319
> Project: Flink
> Issue Type: Improvement
> Components: CEP
> Affects Versions: 1.0.0
> Reporter: Till Rohrmann
> Assignee: Robert Thorman
> Priority: Minor
>
> Adding an {{or}} operator to CEP's pattern API would be beneficial. This
> would considerably extend the set of supported patterns. The {{or}} operator
> lets you define multiple succeeding pattern states for the next stage.
> {code}
> Pattern.begin("start").next("middle1").where(...).or("middle2").where(...)
> {code}
> In order to implement the {{or}} operator, one has to extend the {{Pattern}}
> class. Furthermore, the {{NFACompiler}} has to be extended to generate two
> resulting pattern states in case of an {{or}} operator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
