This worked very well for connecting to non-kerberized clusters, but when I began to test against kerberized clusters I hit the following exception: : Illegal Hadoop Version: Unknown (expected A.B.* format)Īt .(ShimLoader.java:168)Īt .(ShimLoader.java:143)Īt .(ShimLoader.java:129)Īt .(KerberosSaslHelper.java:54)Īt .HiveConnection.createBinaryTransport(HiveConnection.java:414)Īt .HiveConnection.openTransport(HiveConnection.java:191)Īt .HiveConnection.(HiveConnection.java:155)Īt .nnect(HiveDriver.java:105) When I first created this project the intent was to gather all required Hive dependencies into one single jar file to simplify scenarios like the one described here.
You are now ready to execute your first query against Hive using DataGrip!. After creating the "Project Data Source", test the connection. Then add the following flags to "VM Options" on the "Advanced" tab. Make sure you load the hive-jdbc-uber-x.jar that you just downloaded.Ĭreate a new "Project Data Source" using the new Driver. Under "File" > "Data Sources.", create a new Driver. Kinit with an appropriate principal and launch DataGrip You are now ready to execute your first query against Hive using DbVisualizer!. 
You should see something like the following in the "Connection Message" text area if the connection is successful.
Hit the "Connect" button to test the connection. Please note that you must append the "principal" to the "database" parameter for kerberized connections. Hive-jdbc-uber-x.jar that you just downloaded.Ĭreate a new connection ("Database" > "Create Database Connection") and fill out the details based on your cluster as seen below. For the "Driver File Paths" you are pointing to the Open the Diver Manager dialog ("Tools" > "Driver Manager.") and hit the "Create a new driver" icon.įill in the information as seen below. DbVisualizer will need to be restarted after applying these changes. Open DbVisualizer preferences ("DbVisualizer" > "Preferences") and add the following properties. Kinit with an appropriate principal and launch DbVisualizer You can successfully kinit from your workstation against the realm specified in your nf file. You have a valid kerberos principal that can access the appropriate services your cluster. The nf file on your workstation matches the one on your cluster. DbVisualizer and/or DataGrip have been successfully installed on your workstation. You have downloaded the latest release of my Hive JDBC Uber Jar and placed it somewhere sensible. #Dbvisualizer kerberos full#
A full description of these tasks is out of scope for this article, but at a high level, make sure that: There are a few key things that must be properly configured before attempting to connect to a kerberized cluster. Hive JDBC Uber Jar), aim to simplify and standardize this process. This article, in combination with a project I created ( While connecting these tools to clusters without kerberos is relatively straightforward, the process of connecting them to kerberized clusters can be complex and error prone. Although these tools don't offer native Hive support they can be easily configured to connect to Hive using JDBC. SQL development tools like DbVisualizer, SQuirreL SQL and DataGrip are popular options for database development.
0 kommentar(er)
