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 2020/03/05 10:44:00 UTC
[jira] [Resolved] (SPARK-31024) Allow specifying session catalog
name (spark_catalog) in qualified column names
[ https://issues.apache.org/jira/browse/SPARK-31024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-31024.
---------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Issue resolved by pull request 27776
[https://github.com/apache/spark/pull/27776]
> Allow specifying session catalog name (spark_catalog) in qualified column names
> -------------------------------------------------------------------------------
>
> Key: SPARK-31024
> URL: https://issues.apache.org/jira/browse/SPARK-31024
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.0.0, 3.1.0
> Reporter: Terry Kim
> Assignee: Terry Kim
> Priority: Major
> Fix For: 3.0.0
>
>
> Currently, the user cannot specify the session catalog name when using qualified column names for v1 tables:
> {code:java}
> SELECT spark_catalog.default.t.i FROM spark_catalog.default.t
> {code}
> fails with "cannot resolve '`spark_catalog.default.t.i`".
> This is inconsistent with v2 tables where catalog name can be used:
> {code:java}
> SELECT testcat.ns1.tbl.id FROM testcat.ns1.tbl.id
> {code}
--
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