flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-3216) Define pattern specification
Date Mon, 11 Jan 2016 16:15:39 GMT
Till Rohrmann created FLINK-3216:
------------------------------------

             Summary: Define pattern specification
                 Key: FLINK-3216
                 URL: https://issues.apache.org/jira/browse/FLINK-3216
             Project: Flink
          Issue Type: Sub-task
            Reporter: Till Rohrmann


In order to detect event patterns we first have to define the pattern. This issue tracks the
progress of implementing a user facing API to define event patterns. 

Patterns should support the following operations

* next(): The given event has to follow directly after the preceding event
followedBy(): The given event has to follow the preceding event. There might occur other events
in-between
* every(): In a follow-by relationship a starting event can be matched with multiple successive
events. Consider the pattern a → b where → denotes the follow-by relationship. The event
sequence a, b, b can be matched as a, b or a, (b), b where the first b is left out. The essential
question is whether a is allowed to match multiple times or only the first time. The method
every specifies exactly that. Every events in a pattern can match with multiple successive
events. This makes only sense in a follow-by relationship, though.
* followedByEvery(): Similar to followedBy just that the specified element can be matched
with multiple successive events
* or(): Alternative event which can be matched instead of the original event: every(“e1”).where().or(“e2”).where()
* within(): Defines a time interval in which the pattern has to be completed, otherwise an
incomplete pattern can be emitted (timeout case)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message