[HIVE-11581] HiveServer2 should store connection params in ZK when using dynamic service discovery for simpler client connection string.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0, 2.0.0
• Fix Version/s: 1.3.0, 2.0.0
• Component/s: HiveServer2, JDBC
• Labels: TODOC1.3
• Assignee: Vaibhav Gumashta
• Reporter: Vaibhav Gumashta
• Created: 17/Aug/15 18:10
• Updated: 15/Aug/16 20:54
• Resolved: 25/Aug/15 00:16

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:

beeline> !connect jdbc:hive2://vgumashta.local:2181,vgumashta.local:2182,vgumashta.local:2183/;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2 vgumashta vgumashta org.apache.hive.jdbc.HiveDriver

Issue Links

• blocks: NIFI-2575 HiveQL Processors Fail due to invalid JDBC URI resolution when using Zookeeper URI
• is related to: HIVE-11932 JDBC Driver appends an extra "/" when configuring connection by reading httpPath from ZooKeeper
• is related to: HIVE-12280 HiveConnection does not try other HS2 after failure for service discovery
• relates to: HIVE-11555 Beeline sends password in clear text if we miss -ssl=true flag in the connect string
• relates to: HIVE-11875 JDBC Driver does not honor delegation token mechanism when readings params from ZooKeeper
• relates to: HIVE-12500 JDBC driver not overlaying params supplied via properties object when reading params from ZK
• relates to: HIVE-13326 HiveServer2: Make ZK config publishing configurable
• links to: Review Board
• mentioned in: Page Loading...