[ 
https://issues.apache.org/jira/browse/SPARK-30885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Terry Kim updated SPARK-30885:
------------------------------
    Description: 
For the following example,

{code:java}
sql("CREATE TABLE t USING json AS SELECT 1 AS i")
sql("SELECT * FROM spark_catalog.t")
{code}
`spark_catalog.t` is expanded to `spark_catalog.default.t` assuming that the 
current namespace is `default`. However, this is not consistent with V2 
behavior where namespace should be provided if the catalog name is also 
provided.


  was:
For the following example,

{code:java}
sql("CREATE TABLE t USING json AS SELECT 1 AS i")
sql("SELECT * FROM spark_catalog.t")
{code}

works, and `spark_catalog.t` is expanded to `spark_catalog.default.t` assuming 
the current namespace is set to `default`. However, this is not consistent with 
V2 behavior where namespace should be provided if the catalog name is also 
provided.



> V1 table name should be fully qualified
> ---------------------------------------
>
>                 Key: SPARK-30885
>                 URL: https://issues.apache.org/jira/browse/SPARK-30885
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.0.0, 3.1.0
>            Reporter: Terry Kim
>            Priority: Major
>
> For the following example,
> {code:java}
> sql("CREATE TABLE t USING json AS SELECT 1 AS i")
> sql("SELECT * FROM spark_catalog.t")
> {code}
> `spark_catalog.t` is expanded to `spark_catalog.default.t` assuming that the 
> current namespace is `default`. However, this is not consistent with V2 
> behavior where namespace should be provided if the catalog name is also 
> provided.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to