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] [Updated] (HIVE-7342) support hiveserver2,metastore specific config files
Date Wed, 16 Jul 2014 21:07:06 GMT

     [ https://issues.apache.org/jira/browse/HIVE-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thejas M Nair updated HIVE-7342:
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.14.0
           Status: Resolved  (was: Patch Available)

Patch committed to trunk.
Thanks for the reviews Jason, Sushanth and Prasad!


> 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.2#6252)

Mime
View raw message