You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Xiang Li (Jira)" <ji...@apache.org> on 2019/12/17 09:39:00 UTC
[jira] [Commented] (SPARK-29481) all the commands should look up
catalog/table like v2 commands
[ https://issues.apache.org/jira/browse/SPARK-29481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16998026#comment-16998026 ]
Xiang Li commented on SPARK-29481:
----------------------------------
[~cloud_fan] and [~viirya], would you please share your idea why those commands do not support v2 table? Not quite get it after reading the description. Is it doable to change the behavior of v1 and v2 to be identify rather than simply banning them from running?
> all the commands should look up catalog/table like v2 commands
> --------------------------------------------------------------
>
> Key: SPARK-29481
> URL: https://issues.apache.org/jira/browse/SPARK-29481
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Wenchen Fan
> Priority: Major
>
> The newly added v2 commands support multi-catalog and respect the current catalog/namespace. However, it's not true for old v1 commands.
> This leads to very confusing behaviors, for example
> {code}
> USE my_catalog
> DESC t // success and describe the table t from my_catalog
> ANALYZE TABLE t // report table not found as there is no table t in the session catalog
> {code}
> We should make sure all the commands have the same behavior regarding table resolution
--
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