You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Yin Huai (JIRA)" <ji...@apache.org> on 2016/08/26 18:20:21 UTC
[jira] [Resolved] (SPARK-17250) Remove HiveClient and
setCurrentDatabase from HiveSessionCatalog
[ https://issues.apache.org/jira/browse/SPARK-17250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yin Huai resolved SPARK-17250.
------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
Issue resolved by pull request 14821
[https://github.com/apache/spark/pull/14821]
> Remove HiveClient and setCurrentDatabase from HiveSessionCatalog
> ----------------------------------------------------------------
>
> Key: SPARK-17250
> URL: https://issues.apache.org/jira/browse/SPARK-17250
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.1.0
> Reporter: Xiao Li
> Assignee: Apache Spark
> Fix For: 2.1.0
>
>
> This is the first step to clean `HiveClient` from `HiveSessionState`. In the metastore interaction, we always set fully qualified names when accessing/operating a table. That means, we always specify the database. Thus, it is not necessary to use `HiveClient` to change the active database in Hive metastore.
> In `HiveSessionCatalog `, `setCurrentDatabase` is the only function that uses `HiveClient`. Thus, we can remove it after removing `setCurrentDatabase`
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org