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

["Vihang Karajgaonkar (JIRA)" <ji...@apache.org>]

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

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

Adding password to the file could be a security risk. So we should not support password with this configuration file. In case of Kerberos environment, the file could provide the principal. In case of LDAP environment, the password should be prompted to the user when connection is initiated. In default mode of none, an empty password should suffice to connect to the hs2 (so we can skip the password prompt for that mode too)

> 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
>         Attachments: 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)