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] [Resolved] (HIVE-14064) beeline to auto connect to the HiveServer2
Date Tue, 21 Jun 2016 17:07:58 GMT

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

Vihang Karajgaonkar resolved HIVE-14064.
----------------------------------------
    Resolution: Invalid

This got created by mistake with I created HIVE-14063. Discarding it.

> beeline to auto connect to the HiveServer2
> ------------------------------------------
>
>                 Key: HIVE-14064
>                 URL: https://issues.apache.org/jira/browse/HIVE-14064
>             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