hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-7342) support hiveserver2,metastore specific config files
Date Thu, 10 Jul 2014 21:40:04 GMT

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

Thejas M Nair commented on HIVE-7342:
-------------------------------------

[~sushanth] Thanks for prompting me to take a closer look at the precedence! I found an issue,
here is the updated patch.

HIVE-7342.2.patch - With earlier patch hivemetastore-site.xml would take precedence over hiveserver2-site.xml
if embedded metastore is used with hiveserver2, as metastore-site.xml was getting added later.

With this change HiveConf initialization itself would check if embedded metastore is used
and load the hivemetastore-site.xml. This way the order of adding the resources to the Configuration
always remains the same.

Patch also adds tests for both embedded and remote metastore mode. 

The order of predendence (later one takes precedence) : 
hive-site.xml -> hivemetastore-site.xml -> hiveserver2-site.xml -> HiveConf.ConfVars
set through system properties (same as ones set through -hiveconf cmdline params)

> 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