You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2014/09/16 15:48:33 UTC

[jira] [Resolved] (AMBARI-7330) Add HiveServer2 dynamic service discovery configs to Ambari

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

Andrew Onischuk resolved AMBARI-7330.
-------------------------------------
    Resolution: Fixed

Committed to trunk

> Add HiveServer2 dynamic service discovery configs to Ambari
> -----------------------------------------------------------
>
>                 Key: AMBARI-7330
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7330
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 1.7.0
>
>
> To support [HIVE-7935](https://issues.apache.org/jira/browse/HIVE-7935), we're
> adding the following new config params to HiveServer2:  
> 1\. **hive.server2.support.dynamic.service.discovery**  
> default value: false  
> config type: boolean  
> description: Whether HiveServer2 supports dynamic service discovery for its
> clients. To support this, each instance of HiveServer2 currently uses
> ZooKeeper to register itself, when it is brought up. JDBC/ODBC clients should
> use the ZooKeeper ensemble: hive.zookeeper.quorum in their connection string.
> 2\. **hive.server2.zookeeper.namespace**  
> default value: "hiveserver2"  
> config type: String  
> description: The parent node in ZooKeeper used by HiveServer2 when supporting
> dynamic service discovery.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)