[
https://issues.apache.org/jira/browse/BEAM-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175712#comment-17175712
]
Beam JIRA Bot commented on BEAM-9543:
-------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> BeamSQL Pattern Recognization Functionality
> -------------------------------------------
>
> Key: BEAM-9543
> URL: https://issues.apache.org/jira/browse/BEAM-9543
> Project: Beam
> Issue Type: New Feature
> Components: dsl-sql
> Reporter: Rui Wang
> Assignee: Qihang Zeng
> Priority: P2
> Labels: gsoc, gsoc2020, mentor, stale-assigned
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The goal of this Jira is to support the following syntax in BeamSQL:
> {code:sql}
> SELECT T.aid, T.bid, T.cid
> FROM MyTable
> MATCH_RECOGNIZE (
> PARTITION BY userid
> ORDER BY proctime
> MEASURES
> A.id AS aid,
> B.id AS bid,
> C.id AS cid
> PATTERN (A B C)
> DEFINE
> A AS name = 'a',
> B AS name = 'b',
> C AS name = 'c'
> ) AS T
> {code}
> match_recognize is in SQL standard 2016. Currently Calcite also supports it.
> A good reference to match_recognize is [1]
> This will requires touch core components of BeamSQL:
> 1. SQL parser to support the syntax above.
> 2. SQL core to implement physical relational operator.
> 3. Distributed algorithms to implement a list of functions in a distributed
> manner.
> other references:
> Calcite match_recognize syntax [2]
> [1]:
> https://ci.apache.org/projects/flink/flink-docs-stable/dev/table/streaming/match_recognize.html
> [2]: https://calcite.apache.org/docs/reference.html#syntax-1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
