hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vihang Karajgaonkar (JIRA)" <>
Subject [jira] [Commented] (HIVE-14063) beeline to auto connect to the HiveServer2
Date Thu, 30 Jun 2016 19:02:10 GMT


Vihang Karajgaonkar commented on HIVE-14063:

Thanks [~szehon] for your comment. I have attached first draft version of the how the conf
file may look like. We can add more documentation of each parameter in the template file so
that users can understand when each parameter is used. A template file called beeline.conf.template
can be provided in the conf directory and user can use it as a template to create the beeline.conf
at pre-defined set of locations (need to be determined) file is used to store the properties which include lastConnectedUrl when
the user issues a !save command from beeline command line. Once it is saved the user can issue
!reconnect to reconnect to the last connected url. Another way to use default urls is to provide
environment variables starting with BEELINE_URL_<ID> and then issue beeline connect
-u <id>. Key point being user needs to either issue !reconnect or ./beeline connect
-u id command. The objective of providing a default conf file is to provide seemless experience
to the user so that he/she can connect directly by issuing ./beeline (just like hiveCli)

Both these methods are orthogonal so that they both can be independently used without affecting
each other. User can choose one way or the other based on their preference. 

They can co-exist together too such that should take precedence over beeline.conf
file. The reason being user explicitly issues !save command with the intention to reuse it
by issuing !reconnect command. Eg. if the user gets auto-connected using the beeline.conf
file, and issues !save it will create a ~/.beeline/ and it will be used
as long user fires the !reconnect command. In such case the design should detect that
exists and it should not use the default conf file. Since the user explicitly issued !save
command earlier, as long as ~/.beeline/ exists, that file will be used and
user can either issue !reconnect or the complete !connect -u .. url. If however,
does not exist, and beeline.conf exists, beeline will attempt to initiate connection using
the conf file. If none of the files are present current behavior will continue.

[~spena] [~mohitsabharwal] [~sircodesalot] [~lskuff] please review and let us know your thoughts.
Feel free to include anyone who might be interested. Thanks!

> 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