hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vihang Karajgaonkar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-14063) beeline to auto connect to the HiveServer2
Date Wed, 29 Jun 2016 18:17:17 GMT

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

Vihang Karajgaonkar commented on HIVE-14063:
--------------------------------------------

I confirmed that the above approach works fine in a Kerberos enabled cluster with HAproxy
for load-balancing too. Using Zookeeper for load-balancing shouldn't be a problem too as long
the url is has all the information.

In HiveConnection.java

{code:java}
try {
      connParams = Utils.parseURL(uri);
    } catch (ZooKeeperHiveClientException e) {
      throw new SQLException(e);
    }
{code}

The Utils.parseURL method above parses the url string including zookeeper ensemble and service
discovery mode. As long as the url contains all the right information the code path should
be the same.

> beeline to auto connect to the HiveServer2
> ------------------------------------------
>
>                 Key: HIVE-14063
>                 URL: https://issues.apache.org/jira/browse/HIVE-14063
>             Project: Hive
>          Issue Type: Improvement
>          Components: Beeline
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>            Priority: Minor
>
> Currently one has to give an jdbc:hive2 url in order for Beeline to connect a hiveserver2
instance. It would be great if Beeline can get the info somehow (from a properties file at
a well-known location?) and connect automatically if user doesn't specify such a url. If the
properties file is not present, then beeline would expect user to provide the url and credentials
using !connect or ./beeline -u .. commands
> While Beeline is flexible (being a mere JDBC client), most environments would have just
a single HS2. Having users to manually connect into this via either "beeline ~/.propsfile"
or -u or !connect statements is lowering the experience part.



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

Mime
View raw message