You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Aihua Xu (JIRA)" <ji...@apache.org> on 2016/10/17 17:09:58 UTC

[jira] [Updated] (HIVE-14063) beeline to auto connect to the HiveServer2

     [ https://issues.apache.org/jira/browse/HIVE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aihua Xu updated HIVE-14063:
----------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.0
           Status: Resolved  (was: Patch Available)

Pushed to master. Thanks Vihang for the work.

BTW: can you update the doc in the wiki?

> 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
>             Fix For: 2.2.0
>
>         Attachments: HIVE-14063.01.patch, HIVE-14063.02.patch, beeline.conf.template
>
>
> 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)