[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=15414639#comment-15414639 ] 

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

I had a offline discussion with [~dlo]. Copying his comment here for the record.

{quote}
Why is it a problem for there to be more properties in hive-site.xml than you need? Can't you just add what you need to hive-site.xml? Today, hive-site.xml already serves different use-cases that use different subsets of properties, such as the old hive CLI, HS2, and the Hive Metastore Server. It's not a problem that there are HS2-specific properties in that file. 

The most logical place for these configs is to add them to hive-site.xml - the existing standard client config file for hive. I'm sure some users are going to put configs into hive-site.xml and be confused when they have to actually go into this new config file.

When you say a "properties file", you mean it'll be like a java properties file, and NOT a Hadoop XML file? I strongly recommend against this. Hadoop XML is the standard config format, and using something else means you can't leverage standard Hadoop libraries like the Hadoop credential provider.
{quote}

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