hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Mujumdar (JIRA)" <>
Subject [jira] [Commented] (HIVE-4185) Document HiveServer2 JDBC and Beeline CLI in the user documentation
Date Fri, 15 Mar 2013 19:36:13 GMT


Prasad Mujumdar commented on HIVE-4185:

Hive includes a new JDBC client driver for HiveServer2. It supports both embedded and remote
access to HiveServer2.
The JDBC connection URL format has prefix is jdbc:hive2:// and the Driver class is org.apache.hive.jdbc.HiveDriver.
Note that this is different from the old hiveserver. For remote server, the URL format is
jdbc:hive2://<host>:<port>/<db>. For embedded server, the URL format is
jdbc:hive2:// (no host or port)
When connecting to HiveServer2 with kerberos authentication, the URL format is jdbc:hive2://<host>:<port>/<db>;principal=<Server_Principal_of_HiveServer2>.
The client needs to have a valid Kerberos ticket in the ticket cache before connecting. In
case of LDAP or customer pass through authentication, the client needs to pass the valid user
name and password to JDBC connection API.
Beeline Shell -
Hive includes a new command shell Beeline that works with HiveServer2. Its a JDBC client that
is based on SQLLine CLI ( There’s an detailed documentation
of the SQLLine options available at which is applicable
to Beeline.
> Document HiveServer2 JDBC and Beeline CLI in the user documentation 
> --------------------------------------------------------------------
>                 Key: HIVE-4185
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Documentation, HiveServer2
>            Reporter: Prasad Mujumdar
>            Assignee: Prasad Mujumdar
> The user documentation includes
information about client connection to thrift server.
> We need to include HiveServer2 client details (JDBC, Beeline)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message