hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Szehon Ho (JIRA)" <>
Subject [jira] [Commented] (HIVE-14063) beeline to auto connect to the HiveServer2
Date Wed, 22 Jun 2016 23:39:16 GMT


Szehon Ho commented on HIVE-14063:

I think it will be very useful, to have a properties file to allow for auto specification
of properties like url, name, password.  I assume that's the properties that are proposed,
or is there more?  Another idea is to detect a local HS2 and connect to that, but it would
be orthogonal.

Some thoughts on this proposal:

I'm not sure about the need for a --property-file if user can override some properties via
the command line.

A lot of times there is more than one HS2 in a cluster, like HA Proxy or ZK quorum load balancing.
 I assume the proposal also allows for connecting to those URL's as well, to get a random
HS2?  And also for kerberos as well?

One usability issue is that those beeline properties are defined by just a letter like 'u',
'n', 'p'.   Hence it would be confusing in the properties file if the key is different, maybe
its better if beeline itself took more descriptive names in addition to letters to make it

> beeline to auto connect to the HiveServer2
> ------------------------------------------
>                 Key: HIVE-14063
>                 URL:
>             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

View raw message