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-6418) Support for dynamic state changes in CEP patterns
Date Fri, 23 Jun 2017 10:09:02 GMT

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

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

Github user kl0u commented on a diff in the pull request:

    https://github.com/apache/flink/pull/4143#discussion_r123714098
  
    --- Diff: flink-libraries/flink-cep/src/test/java/org/apache/flink/cep/nfa/UntilConditionITCase.java
---
    @@ -0,0 +1,427 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one
    + * or more contributor license agreements.  See the NOTICE file
    + * distributed with this work for additional information
    + * regarding copyright ownership.  The ASF licenses this file
    + * to you under the Apache License, Version 2.0 (the
    + * "License"); you may not use this file except in compliance
    + * with the License.  You may obtain a copy of the License at
    + *
    + *     http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +
    +package org.apache.flink.cep.nfa;
    +
    +import org.apache.flink.cep.Event;
    +import org.apache.flink.cep.nfa.compiler.NFACompiler;
    +import org.apache.flink.cep.pattern.Pattern;
    +import org.apache.flink.cep.pattern.conditions.IterativeCondition;
    +import org.apache.flink.cep.pattern.conditions.SimpleCondition;
    +import org.apache.flink.streaming.runtime.streamrecord.StreamRecord;
    +
    +import com.google.common.collect.Lists;
    +import org.junit.Test;
    +
    +import java.util.ArrayList;
    +import java.util.List;
    +
    +import static org.apache.flink.cep.nfa.NFATestUtilities.compareMaps;
    +import static org.apache.flink.cep.nfa.NFATestUtilities.feedNFA;
    +import static org.junit.Assert.assertTrue;
    +
    +/**
    + * Tests for {@link Pattern#until(IterativeCondition)}.
    + */
    +public class UntilConditionITCase {
    +
    +
    --- End diff --
    
    You could add here the test I mentioned earlier and it can be worth adding a test with
a proper `IterativeCondition` for completeness.


> Support for dynamic state changes in CEP patterns
> -------------------------------------------------
>
>                 Key: FLINK-6418
>                 URL: https://issues.apache.org/jira/browse/FLINK-6418
>             Project: Flink
>          Issue Type: Improvement
>          Components: CEP
>    Affects Versions: 1.3.0
>            Reporter: Elias Levy
>            Assignee: Dawid Wysakowicz
>
> Flink CEP library allows one to define event pattern to match where the match condition
can be determined programmatically via the {{where}} method.  Flink 1.3 will introduce so-called
iterative conditions, which allow the predicate to look up events already matched by the pattern
and thus be conditional on them.
> 1.3 also introduces to the API quantifer methods which allow one to declaratively specific
how many times a condition must be matched before there is a state change.
> Alas, there are use cases where the quantifier must be determined dynamically based on
the events matched by the pattern so far.  Therefore, I propose the adding of a new {{Pattern}}:
{{until}}.
> Like the new iterative variant of {{where}}, {{until}} would take a predicate function
and a context that provides access to events already matched.  But whereas {{where}} determines
if an event is accepted by the pattern, {{until}} determines whether is pattern should move
on to the next state.
> In our particular use case, we have a pattern where an event is matched a number of times,
but depending on the event type, the number (threshold) for the pattern to match is different.
 We could decompose the pattern into multiple similar patterns, but that could be inefficient
if we have many such patterns.  If the functionality of {{until}} were available, we could
make do with a single pattern.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message