[
https://issues.apache.org/jira/browse/CALCITE-6619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888037#comment-17888037
]
Julian Hyde edited comment on CALCITE-6619 at 10/9/24 7:05 PM:
---------------------------------------------------------------
I read your example. I was not aware of
[AutoService|https://github.com/google/auto/blob/main/service/README.md] but it
makes sense.
I would move that code out of the .jj file and into a regular class. Template
code gets duplicated into each generated parser and we don't want that.
was (Author: julianhyde):
I read your example. I was not aware of AutoService but it makes sense.
I would move that code out of the .jj file and into a regular class. Template
code gets duplicated into each generated parser and we don't want that.
> 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)
