You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "yanjing.wang (Jira)" <ji...@apache.org> on 2022/04/01 02:34:00 UTC
[jira] [Commented] (CALCITE-5076) parserConfig is not set correct when use some methods in CalcitePrepareImpl
[ https://issues.apache.org/jira/browse/CALCITE-5076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515677#comment-17515677 ]
yanjing.wang commented on CALCITE-5076:
---------------------------------------
Thanks galaxy, please state the symptom rather the cause, a practical test case will be better. Do not @ a specific person to help the review so that others will back off.
> parserConfig is not set correct when use some methods in CalcitePrepareImpl
> -----------------------------------------------------------------------------
>
> Key: CALCITE-5076
> URL: https://issues.apache.org/jira/browse/CALCITE-5076
> Project: Calcite
> Issue Type: Bug
> Reporter: galaxy yang
> Priority: Major
> Attachments: image-2022-03-31-23-44-44-916.png, image-2022-03-31-23-45-01-468.png, image-2022-03-31-23-45-33-979.png, image-2022-03-31-23-46-46-939.png, image-2022-03-31-23-47-12-377.png
>
>
> when i use org.apache.calcite.prepare.CalcitePrepareImpl#parse_ and org.apache.calcite.prepare.CalcitePrepareImpl.CalcitePreparingStmt#expandView,
> i noticed that in the two methods, the SqlParser uses the default SqlParser.Config, not created from the context。
> it causes that only default sql syntax can be parsed, i set the CalciteConnectionConfig, but not effective.
>
> can the SqlParser.Config created from the context, like the method org.apache.calcite.prepare.CalcitePrepareImpl#prepare2_
>
>
> !image-2022-03-31-23-46-46-939.png|width=615,height=267!
> !image-2022-03-31-23-47-12-377.png|width=511,height=280!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)