[
https://issues.apache.org/jira/browse/HIVE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415977#comment-15415977
]
Vihang Karajgaonkar commented on HIVE-14063:
--------------------------------------------
It is a good suggestion to include these values in hive-site.xml with the
advantages of leveraging existing configuration frameworks to deliver the
configs to Beeline. But IMO there are the following problems with using
hive-site.xml
1. Beeline is in theory a general purpose JDBC client. As far as I understand
it was not designed to be hive-only client. Adding these values to
hive-site.xml is essentially tying this feature to hive specific environments.
While one may argue that Beeline is almost always used for Hive, that is
something that the larger community in general has to decide to whether to
treat it as hive-specific JDBC client or not.
2. Different users could potentially have different connection endpoints like
urls, credentials (even authentication mechanisms for different HS2 instances?)
which means we need to store the user-specific information in some other place
(environment variables/configuration file) I don't see any particular
advantages of using two sources of information for getting a few configuration
values since we will have to read both the files in any case. Similarly, user
specific configurations like hive variables and hiveConf need to be separated
from the the all-purpose general hive-site.xml. All this file will contain is
the user-friendly way to describe connection url (which includes hosts,
authentication, default db, hivevars and user-specific hiveConf)
> 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)
