You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ivan Mushketyk (JIRA)" <ji...@apache.org> on 2016/08/03 06:40:20 UTC

[jira] [Commented] (FLINK-3703) Add sequence matching semantics to discard matched events

    [ https://issues.apache.org/jira/browse/FLINK-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405423#comment-15405423 ] 

Ivan Mushketyk commented on FLINK-3703:
---------------------------------------

Hi,

Do you have an idea how a code example with this feature would look like?

> Add sequence matching semantics to discard matched events
> ---------------------------------------------------------
>
>                 Key: FLINK-3703
>                 URL: https://issues.apache.org/jira/browse/FLINK-3703
>             Project: Flink
>          Issue Type: Improvement
>          Components: CEP
>    Affects Versions: 1.0.0, 1.1.0
>            Reporter: Till Rohrmann
>            Priority: Minor
>
> There is no easy way to decide whether events can be part of multiple matching sequences or not. Currently, the default is that an event can participate in multiple matching sequences. E.g. if you have the pattern {{Pattern.<Event>begin("a").followedBy("b")}} and the input event stream {{Event("A"), Event("B"), Event("C")}}, then you will generate the following matching sequences: {{Event("A"), Event("B")}}, {{Event("A"), Event("C")}} and {{Event("B"), Event("C")}}. 
> It would be useful to allow the user to define where the matching algorithm should continue after a matching sequence has been found. Possible option values could be 
>  * {{from first}} - continue keeping all events for future matches (that is the current behaviour) 
>  * {{after first}} -  continue after the first element (remove first matching event and continue with the second event)
>  * {{after last}} - continue after the last element (effectively discarding all elements of the matching sequence)



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