You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2021/04/15 00:08:00 UTC
[jira] [Commented] (CALCITE-4535) ServerDdlExecutor cannot execute
DROP commands with qualified object names
[ https://issues.apache.org/jira/browse/CALCITE-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321818#comment-17321818 ]
Julian Hyde commented on CALCITE-4535:
--------------------------------------
Reviewing & testing now. Notwithstanding some quibbles about test method names, this looks good and I will merge shortly.
> ServerDdlExecutor cannot execute DROP commands with qualified object names
> --------------------------------------------------------------------------
>
> Key: CALCITE-4535
> URL: https://issues.apache.org/jira/browse/CALCITE-4535
> Project: Calcite
> Issue Type: Bug
> Components: server
> Affects Versions: 1.26.0
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> Consider the query {{DROP TABLE s.t}}. The {{ServerDdlExecutor}} will attempt to resolve the default schema path, and the would try to invoke {{SqlIdentifier.getSimple}} on the {{s.t}} identifier. When assertions are enabled this would lead to an AssertionError. When assertions are disabled this would lead to an incorrectly resolved table name: {{s}} instead of {{t}}.
> All {{DROP}} commands are affected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)