[
https://issues.apache.org/jira/browse/FLINK-10232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16836825#comment-16836825
]
Danny Chan commented on FLINK-10232:
------------------------------------
Hi, [~suez1224], I'm Danny from Blink SQL team, we have a module named
*flink-sql-parser* to handle the sql parsing which includes all the DDLs and
DMLs, i saw that there are many comments on your design doc[1], and there are
still few disputes on the DDL grammar of streaming tables. But for batch, we
have make agreement cause it is almost standard.
So i'm wondering if we can make some progress. Saying, we can contribute the
DDLs for batch firstly. I kind of want to know your work for this issue to see
if we can make some cooperation.
Thx again for firing the discussion and detailed design doc, hoping for your
suggestions.
[1]
[https://docs.google.com/document/d/1TTP-GCC8wSsibJaSUyFZ_5NBAHYEB1FVmPpP7RgDGBA/edit#heading=h.wpsqidkaaoil]
> Add a SQL DDL
> -------------
>
> Key: FLINK-10232
> URL: https://issues.apache.org/jira/browse/FLINK-10232
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Reporter: Timo Walther
> Assignee: Shuyi Chen
> Priority: Major
>
> This is an umbrella issue for all efforts related to supporting a SQL Data
> Definition Language (DDL) in Flink's Table & SQL API.
> Such a DDL includes creating, deleting, replacing:
> - tables
> - views
> - functions
> - types
> - libraries
> - catalogs
> If possible, the parsing/validating/logical part should be done using
> Calcite. Related issues are CALCITE-707, CALCITE-2045, CALCITE-2046,
> CALCITE-2214, and others.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
