diff options
| author | gatorsmile <gatorsmile@gmail.com> | 2016-08-26 11:19:03 -0700 |
|---|---|---|
| committer | Yin Huai <yhuai@databricks.com> | 2016-08-26 11:19:03 -0700 |
| commit | 261c55dd8808502fb7f3384eb537d26a4a8123d7 (patch) | |
| tree | ab8810fdacc2451fdf19a97d5ea8b16741dc3532 /sql/core/src/test/scala | |
| parent | fd4ba3f626f49d7d616a2a334d45b1c736e1db1c (diff) | |
| download | spark-261c55dd8808502fb7f3384eb537d26a4a8123d7.tar.gz spark-261c55dd8808502fb7f3384eb537d26a4a8123d7.tar.bz2 spark-261c55dd8808502fb7f3384eb537d26a4a8123d7.zip | |
[SPARK-17250][SQL] Remove HiveClient and setCurrentDatabase from HiveSessionCatalog
### What changes were proposed in this pull request?
This is the first step to remove `HiveClient` from `HiveSessionState`. In the metastore interaction, we always use the fully qualified table name 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`
### How was this patch tested?
The existing test cases.
Author: gatorsmile <gatorsmile@gmail.com>
Closes #14821 from gatorsmile/setCurrentDB.
Diffstat (limited to 'sql/core/src/test/scala')
0 files changed, 0 insertions, 0 deletions