You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2014/11/18 08:04:34 UTC
[jira] [Commented] (HIVE-7342) support hiveserver2,metastore
specific config files
[ https://issues.apache.org/jira/browse/HIVE-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215805#comment-14215805 ]
Thejas M Nair commented on HIVE-7342:
-------------------------------------
Added doc in https://cwiki.apache.org/confluence/display/Hive/AdminManual+Configuration#AdminManualConfiguration-ConfiguringHive
> 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
> Fix For: 0.14.0
>
> 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, hivemetastore-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.3.4#6332)