flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3703) Add sequence matching semantics to discard matched events
Date Tue, 15 Nov 2016 11:09:58 GMT

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

ASF GitHub Bot commented on FLINK-3703:
---------------------------------------

Github user mushketyk commented on the issue:

    https://github.com/apache/flink/pull/2367
  
    Hi @LordFB 
    
    I don't think there is currently a way to do it in cep-flink. I am still waiting for Till's
review for this PR, but he seems to be really busy with other work.
    
    Maybe together we will be able to convince him to spend some time on reviewing this and
similar CEP PRs.


> 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
>            Assignee: Ivan Mushketyk
>            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)

Mime
View raw message