ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7330) Add HiveServer2 dynamic service discovery configs to Ambari
Date Tue, 16 Sep 2014 14:17:33 GMT

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

Hudson commented on AMBARI-7330:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #255 (See [https://builds.apache.org/job/Ambari-trunk-Commit/255/])
AMBARI-7330. Add HiveServer2 dynamic service discovery configs to Ambari (aonishuk) (aonishuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a8fb52f33c3137313b8651590b828e1cad3da7ff)
* ambari-server/src/main/resources/stacks/HDP/1.3.2/services/HIVE/configuration/hive-site.xml
* ambari-server/src/main/resources/stacks/HDP/2.0.6/services/HIVE/configuration/hive-site.xml
* ambari-web/app/data/HDP2/site_properties.js
* ambari-server/src/main/resources/stacks/HDP/2.1.GlusterFS/services/HIVE/configuration/hive-site.xml
* ambari-web/app/data/site_properties.js
* ambari-server/src/main/resources/stacks/HDP/2.1/services/HIVE/configuration/hive-site.xml


> 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)

Mime
View raw message