[
https://issues.apache.org/jira/browse/HIVE-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064062#comment-14064062
]
Prasad Mujumdar commented on HIVE-7342:
---------------------------------------
I guess treating hive-site as base file should be sufficient. It's unlikely
that you will have variety of metastore setups (embedded and remote, or secure
and unsecure) in a single deployment. Thanks for updating the release notes!
+1
> 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,
> 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.2#6252)
