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-7062) Support the basic functionality of MATCH_RECOGNIZE
Date Wed, 10 Oct 2018 12:42:00 GMT

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

ASF GitHub Bot commented on FLINK-7062:

dawidwys opened a new pull request #6815:  [FLINK-7062] Added basic support for MATCH_RECOGNIZE
URL: https://github.com/apache/flink/pull/6815
   ## What is the purpose of the change
   This commit adds basic support of MATCH_RECOGNIZE to SQL using CEP library. It is a follow
up of work from @dianfu from PR: #4502 
   ## Brief change log
     - translating MATCH_RECOGNIZE to CEP library building blocks
     -  9ba70a8 -  changed names assigned to CEP operators to distinguish between keyed and
     - b2afb2a - fixed return type when time indicator is a result from aggregation
     - da8c225 - throw exception when we were to skip to first element of match 
   ## Verifying this change
   This change added tests and can be verified as follows:
     - Validation tests: 
       - org.apache.flink.table.api.stream.sql.validation.MatchValidationTest
       - org.apache.flink.table.runtime.stream.sql.MatchRecognizeITCase (validations that
are performed only during plan translation)
       - org.apache.flink.table.`match`.MatchRecognizeTest (validations that are performed
during pattern translation)
     - Query translation: org.apache.flink.table.api.stream.sql.MatchRecognizeTest
     - IT cases: org.apache.flink.table.runtime.stream.sql.MatchRecognizeITCase
     - Translation from MATCH_RECOGNIZE to CEP patterns: org.apache.flink.table.`match`.MatchRecognizeTest
   ## 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)
     - documentation will be added in subsequent PR

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:

> Support the basic functionality of MATCH_RECOGNIZE
> --------------------------------------------------
>                 Key: FLINK-7062
>                 URL: https://issues.apache.org/jira/browse/FLINK-7062
>             Project: Flink
>          Issue Type: Sub-task
>          Components: CEP, Table API &amp; SQL
>            Reporter: Dian Fu
>            Assignee: Dian Fu
>            Priority: Major
>              Labels: pull-request-available
> In this JIRA, we will support the basic functionality of {{MATCH_RECOGNIZE}} in Flink
SQL API which includes the support of syntax {{MEASURES}}, {{PATTERN}} and {{DEFINE}}. This
would allow users write basic cep use cases with SQL like the following example:
> {code}
> SELECT T.aid, T.bid, T.cid
> FROM MyTable
>     A.id AS aid,
>     B.id AS bid,
>     C.id AS cid
>     A AS A.name = 'a',
>     B AS B.name = 'b',
>     C AS C.name = 'c'
> ) AS T
> {code}

This message was sent by Atlassian JIRA

View raw message