[ https://issues.apache.org/jira/browse/CALCITE-6619 ]
赵祥钰 deleted comment on CALCITE-6619:
------------------------------
was (Author: JIRAUSER307296):
[~julianhyde] I found that I could simply use SqlDdl instead of DdlExecutorImpl
to override the execut method in the corresponding class such as
SqlCreateTable, SqlCreateView, I wrote a new [Demo
|https://github.com/apache/calcite/commit/64a2b294df04aa775186a82add04df3ba2141c83]
I hope you can take a look. At present, because I am not clear about the logic
of the within-distinct.iq test file, only two points failed the test. Focus on
these
changes：org.apache.calcite.prepare.CalcitePrepareImpl#executeDdl、org.apache.calcite.sql.SqlDdl、org.apache.calcite.sql.ddl.SqlCreateTable#execute
> DDL statement executor extension
> --------------------------------
>
> Key: CALCITE-6619
> URL: https://issues.apache.org/jira/browse/CALCITE-6619
> Project: Calcite
> Issue Type: New Feature
> Components: server
> Affects Versions: 1.37.0
> Reporter: 赵祥钰
> Priority: Major
>
> The current DDL actuator implementation code is written dead, and not
> according to the existing factory pattern design, I want to expand the
> implementation class of each module through Java Server Faces, DDL can be
> extended in mongodb, kafka, redis and other sub-modules, so that DDL is not
> limited to the statement parsing stage
> I give Demon for you to evaluate the feasibility
> ,[Demon|https://github.com/apache/calcite/compare/main...zhaoxiangyublzcat:calcite:Extended-ddl]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
