You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Mariano Dominguez (JIRA)" <ji...@apache.org> on 2014/08/28 23:29:09 UTC
[jira] [Updated] (HIVE-7903) [Documentation] Remove
hive.metastore.warehouse.dir from Client Configuration Parameters list in
Remote Metastore section
[ https://issues.apache.org/jira/browse/HIVE-7903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mariano Dominguez updated HIVE-7903:
------------------------------------
Description:
Source: https://cwiki.apache.org/confluence/display/Hive/AdminManual+MetastoreAdmin#AdminManualMetastoreAdmin-RemoteMetastore
In Remote Metastore deployment mode, neither the Hive CLI nor the Beeline can change the value of the ‘hive.metastore.warehouse.dir’ property because it is a “server-side” property.
Changing the value can be accomplished, however, by running in Local Metastore mode (that is, bypassing the Hive Metastore Server and directly accessing the Metastore database):
1) At runtime
$ hive --hiveconf hive.metastore.warehouse.dir=<path> -e “<query>”
$ beeline --hiveconf hive.metastore.warehouse.dir=<path> -n <username> -p <password> -u <connection_string> -e "<query>"
2) In the shell
hive > SET hive.metastore.warehouse.dir=<path>;
beeline > SET hive.metastore.warehouse.dir=<path>;
3) From configuration file: hive-site.xml
This property gets cached once a table/database is created; therefore, subsequent value changes will not take effect. You will need to start a new session to re-set the property.
was:
Source: https://cwiki.apache.org/confluence/display/Hive/AdminManual+MetastoreAdmin#AdminManualMetastoreAdmin-RemoteMetastore
In Remote Metastore deployment mode, neither the Hive CLI nor the Beeline can change the value of the ‘hive.metastore.warehouse.dir’ property because it is a “server-side” property.
Changing the value can be accomplished, however, by running in Local Metastore mode (that is, bypassing the Hive Metastore Server and directly accessing the Metastore database):
1) At runtime
$ hive --hiveconf hive.metastore.warehouse.dir=<path> -e “<query>”
$ beeline --hiveconf hive.metastore.warehouse.dir=<path> -n <username> -p <password> -u <connection_string> -e <query>
2) In the shell
hive > SET hive.metastore.warehouse.dir=<path>;
beeline > SET hive.metastore.warehouse.dir=<path>;
3) From configuration file: hive-site.xml
This property gets cached once a table/database is created; therefore, subsequent value changes will not take effect. You will need to start a new session to re-set the property.
> [Documentation] Remove hive.metastore.warehouse.dir from Client Configuration Parameters list in Remote Metastore section
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-7903
> URL: https://issues.apache.org/jira/browse/HIVE-7903
> Project: Hive
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 0.12.0
> Reporter: Mariano Dominguez
>
> Source: https://cwiki.apache.org/confluence/display/Hive/AdminManual+MetastoreAdmin#AdminManualMetastoreAdmin-RemoteMetastore
> In Remote Metastore deployment mode, neither the Hive CLI nor the Beeline can change the value of the ‘hive.metastore.warehouse.dir’ property because it is a “server-side” property.
> Changing the value can be accomplished, however, by running in Local Metastore mode (that is, bypassing the Hive Metastore Server and directly accessing the Metastore database):
> 1) At runtime
> $ hive --hiveconf hive.metastore.warehouse.dir=<path> -e “<query>”
> $ beeline --hiveconf hive.metastore.warehouse.dir=<path> -n <username> -p <password> -u <connection_string> -e "<query>"
> 2) In the shell
> hive > SET hive.metastore.warehouse.dir=<path>;
> beeline > SET hive.metastore.warehouse.dir=<path>;
> 3) From configuration file: hive-site.xml
> This property gets cached once a table/database is created; therefore, subsequent value changes will not take effect. You will need to start a new session to re-set the property.
--
This message was sent by Atlassian JIRA
(v6.2#6252)