[
https://issues.apache.org/jira/browse/FLINK-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555222#comment-16555222
]
Timo Walther commented on FLINK-6935:
-------------------------------------
Thanks for renewing the discussion. Sorry, that this feature has not received
more attention in the last couple of months. We still want to have this feature
in Flink. Actually, it was on my list for Flink 1.6 but couldn't make it. We
should aim for Flink 1.7. [~dawidwys] aligned the CEP side for
{{MATCH_RECOGNIZE}}. The PR itself should not have many merge conflicts, so we
can review it soon. See also the recent discussion
[here|https://twitter.com/julianhyde/status/1021472015478214656].
> Integration of SQL and CEP
> --------------------------
>
> Key: FLINK-6935
> URL: https://issues.apache.org/jira/browse/FLINK-6935
> Project: Flink
> Issue Type: New Feature
> Components: CEP, Table API & SQL
> Reporter: Jark Wu
> Assignee: Dian Fu
> Priority: Major
>
> Flink's CEP library is a great library for complex event processing, more and
> more customers are expressing their interests in it. But it also has some
> limitations that users usually have to write a lot of code even for a very
> simple pattern match use case as it currently only supports the Java API.
> CEP DSLs and SQLs strongly resemble each other. CEP's additional features
> compared to SQL boil down to pattern detection. So It will be awesome to
> consolidate CEP and SQL. It makes SQL more powerful to support more usage
> scenario. And it gives users the ability to easily and quickly to build CEP
> applications.
> The FLIP can be found here:
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-20%3A+Integration+of+SQL+and+CEP
> This is an umbrella issue for the FLIP. We should wait for Calcite 1.13 to
> start this work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
