You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Terry Kim (Jira)" <ji...@apache.org> on 2020/09/16 21:46:00 UTC
[jira] [Commented] (SPARK-30283) V2 Command logical plan should use
UnresolvedV2Relation for a table
[ https://issues.apache.org/jira/browse/SPARK-30283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197249#comment-17197249 ]
Terry Kim commented on SPARK-30283:
-----------------------------------
[~cloud_fan], this work stopped when alter table hit a bump in the road, but should we resume the work for commands like "drop table", etc., whose v2 behavior is different from v1? WDYT?
> V2 Command logical plan should use UnresolvedV2Relation for a table
> -------------------------------------------------------------------
>
> Key: SPARK-30283
> URL: https://issues.apache.org/jira/browse/SPARK-30283
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Terry Kim
> Priority: Major
>
> For the following v2 commands, multi-part names are directly passed to the command without looking up temp views, thus they are always resolved to tables:
> * DROP TABLE
> * REFRESH TABLE
> * RENAME TABLE
> * REPLACE TABLE
> They should be updated to have UnresolvedV2Relation such that temp views are looked up first in Analyzer.ResolveTables.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org