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

Wenchen Fan resolved SPARK-33965.
---------------------------------
    Fix Version/s: 3.2.0
       Resolution: Fixed

Issue resolved by pull request 30997
[https://github.com/apache/spark/pull/30997]

> CACHE TABLE does not support `spark_catalog` in Hive table names
> ----------------------------------------------------------------
>
>                 Key: SPARK-33965
>                 URL: https://issues.apache.org/jira/browse/SPARK-33965
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 3.2.0
>            Reporter: Maxim Gekk
>            Assignee: Maxim Gekk
>            Priority: Major
>             Fix For: 3.2.0
>
>
> The test fails:
> {code:scala}
>   test("SPARK-XXXXX: cache table in spark_catalog") {
>     withNamespace("spark_catalog.ns") {
>       sql("CREATE NAMESPACE spark_catalog.ns")
>       val t = "spark_catalog.ns.tbl"
>       withTable(t) {
>         sql(s"CREATE TABLE $t (col int)")
>         assert(!spark.catalog.isCached(t))
>         sql(s"CACHE TABLE $t")
>         assert(spark.catalog.isCached(t))
>       }
>     }
>   }
> {code}
> with the exception:
> {code:java}
> [info] - SPARK-XXXXX: cache table in spark_catalog *** FAILED *** (278 
> milliseconds)
> [info]   org.apache.spark.sql.AnalysisException: spark_catalog.ns.tbl is not 
> a valid TableIdentifier as it has more than 2 name parts.
> [info]   at 
> org.apache.spark.sql.connector.catalog.CatalogV2Implicits$MultipartIdentifierHelper.asTableIdentifier(CatalogV2Implicits.scala:130)
> [info]   at 
> org.apache.spark.sql.hive.test.TestHiveQueryExecution.$anonfun$analyzed$1(TestHive.scala:600)
> {code}



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