[jira] [Commented] (FLINK-10414) Add skip to next strategy

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

dawidwys opened a new pull request #6756: [FLINK-10414] Added skip to next strategy
URL: https://github.com/apache/flink/pull/6756
 
 
   ## What is the purpose of the change
   
   This pull request adds support of SKIP_TO_NEXT, which will fully cover all variants of AFTER MATCH clause in SQL. This clause is important for e.g. reluctant quantifiers at the end, as after first, shortest match, all others started at the same element will be discarded.
   
   ## Brief change log
   
     * Added `SkipToNextStrategy`
     * Extended documentation with SKIP_TO_NEXT description
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   * `org.apache.flink.cep.nfa.AfterMatchSkipITCase#testNoSkipWithQuantifierAtTheEnd`
   * `org.apache.flink.cep.nfa.AfterMatchSkipITCase#testSkipToNextWithQuantifierAtTheEnd`
   * `org.apache.flink.cep.nfa.AfterMatchSkipITCase#testNoSkipWithFollowedByAny`
   * `org.apache.flink.cep.nfa.AfterMatchSkipITCase#testSkipToNextWithFollowedByAny`
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (**yes** / no)
     - If yes, how is the feature documented? (not applicable / **docs** / **JavaDocs** / not documented)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Add skip to next strategy
> -------------------------
>
>                 Key: FLINK-10414
>                 URL: https://issues.apache.org/jira/browse/FLINK-10414
>             Project: Flink
>          Issue Type: Improvement
>          Components: CEP
>            Reporter: Dawid Wysakowicz
>            Assignee: Dawid Wysakowicz
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.0
>
>
> Add skip to next strategy, that should discard all partial matches that started with the same element as found match.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)