[
https://issues.apache.org/jira/browse/CALCITE-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888166#comment-17888166
]
赵祥钰 commented on CALCITE-6619:
------------------------------
[~julianhyde]
The code from the parser. Jj migrated to SqlParserImplFactorydd getDdlExecutor
without difficulty.
About you mentioned AvaticaUtils. InstantiatePlugin whether can be replaced,
Because autoService needs to be annotated in the sunken implementation class,
or if you use native JSF you need to write a full pathname file in the
META-INF/service directory, but FACTORY currently cannot use JSF in each
ParserImp attribute (unless it is isolated as a separate class), The DataSource
is also obtained through the instantiatePlugin method you mentioned, but we
can't modify the various DataSource implementation classes to add this
annotation, so we need to think about how to extend the SqlParserImplFactory
> 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)
