SELECT and DML are standardized, but DDL tends to be database-specific, so our policy is that you make DDL extensions outside of Calcite. See https://issues.apache.org/jira/browse/CALCITE-609 <https://issues.apache.org/jira/browse/CALCITE-609> for example. You should be able to copy work that has already been done in Drill and Phoenix in extending Calcite’s core parser for DDL.
> On Jun 27, 2016, at 5:51 AM, Zhangrucong <[email protected]> wrote: > > I think Only DDL need parser by yourself > Calcite support DML parser. > > -----邮件原件----- > 发件人: Cody Innowhere [mailto:[email protected]] > 发送时间: 2016年6月27日 20:17 > 收件人: [email protected] > 主题: Re: [QUESTION] Does Calcite support parsing DDL like CREATE TABLE ? > > does this mean I have to do the lexical parsing as well as semantic parsing > all by myself if I want this functionality? > > On Mon, Jun 27, 2016 at 7:38 PM, Zhangrucong <[email protected]> wrote: > >> Calcite does not support parser DDL. >> you must parser DDL and register the stream or table schema to calcite >> by using calcite API. >> >> >> -----邮件原件----- >> 发件人: Jark Wu [mailto:[email protected]] >> 发送时间: 2016年6月27日 19:24 >> 收件人: [email protected] >> 主题: [QUESTION] Does Calcite support parsing DDL like CREATE TABLE ? >> >> Hi, >> >> I want to use calcite to parse some DDL statements like “CREATE >> TABLE”, “CREATE FUNCTION”, “INSERT TABLE” and so on. I tried to use >> PlannerImpl to parse the DDL statement, but it throws exception that >> do not know “CREATE”. >> >> So my question is that does Calcite support parsing DDL? If not , >> how can I support it myself? >> >> >> - Jark Wu >> >>
