You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2019/10/15 16:09:00 UTC

[jira] [Created] (SPARK-29481) all the commands should respect the current catalog/namespace

Wenchen Fan created SPARK-29481:
-----------------------------------

             Summary: all the commands should respect the current catalog/namespace
                 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


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 // fails 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