The Simba Hive ODBC Driver is used for direct SQL and HiveQL access to Apache Hadoop / Hive distributions, enabling Business Intelligence (BI), analytics, and reporting on Hadoop / Hive-based data.
In this blog, we’ll walk you through configuring the Simba Hive ODBC driver for Windows.
The most common way to configure an ODBC driver on Windows is to create a data source name, also known as DSN. This is done by using the ODBC data source administrator program that comes with your install of Windows.
To get started, search ODBC
There are two versions of the ODBC data source administrator app installed. One for each bit-ness. Be sure to use the version that matches the bit-ness of the driver and the application you want to use.
Before the configuration, check that the driver is installed by viewing the Drivers Tab.
If the driver does not appear in this tab, you’ll need to install it to proceed. You can double check the driver install in the Drivers Tab. The installed driver should show up here if you installed successfully.
OPTIONS: You have the option to configure a user or a system DSN. For this demo, we’ve created a system DSN. The process is the same for a user DSN.
Click on the Add button to add list of drivers
The DSN configuration dialog is where you set your connection settings. The first setting allows you to set the data source name, which is the name for the connection that will appear in the application DSN list.
- Click the Add button to display a list of drivers installed. Double click or click Finish to launch the DSN configuration dialog.
Note: This text box will be blocked out and you will not be able to edit it from here. The next field is an optional description where you make comments or notes about your DSN.
To connect to a Hive server:
Configure the Simba Hive ODBC Driver to use the authentication mechanism that matches the access requirements of the server and provides the necessary credentials. By default, the Hive server type is Hive Server 2. Hive Server 1 instances do not support authentication, so you must use No Authentication as the authentication mechanism for Hive Server 1 instances.
OPTION: The Service discovery mode option specifies whether the driver uses the ZooKeeper service. In our demo case, we are using Hive Server 2 and no discovery mode.
- In the Host(s) field, type the IP address or host name of the Hive server.
- In the Port field, type the number of the TCP that the Hive server uses to listen for client connections.
- In the Database field, type the name of the database schema to use when a schema is not explicitly specified in a query. You can still issue queries on other schemas by explicitly specifying the schema in the query.
- Choose the appropriate option, in this case, username and password, and enter your credentials.
- In password options, you can select encrypt password for current user only or all users of the machine. For this demo, we select current user only.
- Optionally, if the operations against Hive are to be done on behalf of a user that is different than the authenticated user for the connection, type the name of the user to be delegated in the Delegation UID field.
- In the Thrift Transport drop-down list, select the transport protocol to use in the Thrift layer.
Proxy & SSL Options
Simba supports various proxy and SSL options; more detailed information can be found in our documentation for our entire line of drivers. Our Hive ODBC driver also supports numerous advanced options which can be found in the advanced options dialog.
- To save your settings and close the Advanced Options dialog box, click OK.
Simba drivers support six (6) levels of logging, which can be found in the logging options of the driver. If you are debugging an issue with Magnitude Simba support, we will frequently ask you for trace logs to aid in reproducing the issue.
For Trace logs:
- Set the log level to trace and then browse for a location to store your trace log.
- A good location for the trace log is documents or downloads or a folder that has relatively open user permissions. It’s important to turn logging off when you are not debugging because the trace level logging can have a massive impact on driver performance.
- Once your DSN is configured, click the Test button, which checks to ensure your driver can successfully connect the Hive server. If that passes, you have successfully configured your driver!
- To save your driver, simply click the OK
That’s it. Now your Hive ODBC driver is configured and ready for use with any application.
To learn more, please visit our Resources or reach out to us at firstname.lastname@example.org.