[
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-deprioritized-major auto-deprioritized-minor auto-unassigned
(was: auto-deprioritized-major auto-unassigned stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned
>
> 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.20.10#820010)
