hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushanth Sowmyan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-7342) support hiveserver2,metastore specific config files
Date Tue, 15 Jul 2014 19:41:05 GMT

    [ https://issues.apache.org/jira/browse/HIVE-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062543#comment-14062543
] 

Sushanth Sowmyan commented on HIVE-7342:
----------------------------------------

I'm +1 on the .2.patch.

Having said that, I also wanted to bring up one more possible corner case that seems to exist,
one that I do not think needs solving(at least not right away - might be worth opening a follow
up to declare if a confvar can be overridden by a conf or not), but one that exists anyway.

Consider the case of a hive client, that loads a hive-site.xml, and finds that the metastore
uris parameter is blank. Thus, it expects that it is a local metastore operation, and thus,
loads hivemetastore-site.xml. In this config, however, say the uris parameter is not blank.
Then, at connect time, that hive client will act upon the uris value, which tells it that
it is not a local metastore, and connects out to the referred url. However, this hive client
has now loaded the metastore conf for other parameters, while still being a remote client
that talks to a metastore.

> support hiveserver2,metastore specific config files
> ---------------------------------------------------
>
>                 Key: HIVE-7342
>                 URL: https://issues.apache.org/jira/browse/HIVE-7342
>             Project: Hive
>          Issue Type: Bug
>          Components: Configuration, HiveServer2, Metastore
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>         Attachments: HIVE-7342.1.patch, HIVE-7342.2.patch
>
>
> There is currently a single configuration file for all components in hive. ie, components
such as hive cli, hiveserver2 and metastore all read from the same hive-site.xml. 
> It will be useful to have a server specific hive-site.xml, so that you can have some
different configuration value set for a server. For example, you might want to enabled authorization
checks for hiveserver2, while disabling the checks for hive cli. The workaround today is to
add any component specific configuration as a commandline (-hiveconf) argument.
> Using server specific config files (eg hiveserver2-site.xml, metastore-site.xml) that
override the entries in hive-site.xml will make the configuration much more easy to manage.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message