[
https://issues.apache.org/jira/browse/HIVE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396329#comment-15396329
]
Naveen Gangam commented on HIVE-14063:
--------------------------------------
[~vihangk1] This will be useful as user move from CLI to beeline and looking
for similar user experience. Thanks for putting this together.
I have a couple of comments
1) I think it will be more useful to make the default properties file be
specific to a user and should be someplace under the ${user.home} aka user's
home directory (quick suggestion ~/.beeline/whateverfilename.properties) . This
prevents users having to overwrite each other's files and allows them to run
their jobs simultaneously across different HS2 instances. It is very realistic
to have users from different projects using a shared cluster be assigned to
different HS2 instance.
2) Having the password in this file is a big concern of mine too. However, it
is always a good practice on the user's behalf to take away read permissions to
any files that might contain passwords. In lieu of #1, it allows users to
control file permissions to the file thats owned by them (in their home
directories). So if we choose to support passwords in the future, there will be
no changes to the file location.
3) Minor point, since there has been a couple of comments on what the file name
should be, though I would offer my thoughts. Since the file really contains
connection properties for HS2, (and because beeline.properties is already
taken), perhaps something like default-hiveserver.properties or
hiveserver-connection.properties or default-hs2-connection.properties or
something alike?
> 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)
