[
https://issues.apache.org/jira/browse/HIVE-11581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vaibhav Gumashta updated HIVE-11581:
------------------------------------
Description:
Currently, the client needs to specify several parameters based on which an
appropriate connection is created with the server. In case of dynamic service
discovery, when multiple HS2 instances are running, it is much more usable for
the server to add its config parameters to ZK which the driver can use to
configure the connection, instead of the jdbc/odbc user adding those in
connection string.
However, at minimum, client will need to specify zookeeper ensemble and that
she wants the JDBC driver to use ZooKeeper:
{noformat}
beeline> !connect
jdbc:hive2://vgumashta.local:2181,vgumashta.local:2182,vgumashta.local:2183/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2
vgumashta vgumashta org.apache.hive.jdbc.HiveDriver
{noformat}
was:Currently, the client needs to specify several parameters based on which
an appropriate connection is created with the server. In case of dynamic
service discovery, when multiple HS2 instances are running, it is much more
usable for the server to add its config parameters to ZK which the driver can
use to configure the connection, instead of the jdbc/odbc user adding those in
connection string.
> HiveServer2 should store connection params in ZK when using dynamic service
> discovery for simpler client connection string.
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-11581
> URL: https://issues.apache.org/jira/browse/HIVE-11581
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, JDBC
> Affects Versions: 1.3.0, 2.0.0
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Attachments: HIVE-11581.1.patch
>
>
> Currently, the client needs to specify several parameters based on which an
> appropriate connection is created with the server. In case of dynamic service
> discovery, when multiple HS2 instances are running, it is much more usable
> for the server to add its config parameters to ZK which the driver can use to
> configure the connection, instead of the jdbc/odbc user adding those in
> connection string.
> However, at minimum, client will need to specify zookeeper ensemble and that
> she wants the JDBC driver to use ZooKeeper:
> {noformat}
> beeline> !connect
> jdbc:hive2://vgumashta.local:2181,vgumashta.local:2182,vgumashta.local:2183/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2
> vgumashta vgumashta org.apache.hive.jdbc.HiveDriver
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
