[
https://issues.apache.org/jira/browse/FLINK-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-6935:
----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Integration of SQL and CEP
> --------------------------
>
> Key: FLINK-6935
> URL: https://issues.apache.org/jira/browse/FLINK-6935
> Project: Flink
> Issue Type: New Feature
> Components: Library / CEP, Table SQL / API
> Reporter: Jark Wu
> Priority: Major
> Labels: auto-unassigned, stale-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
(v8.3.4#803005)
