hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <>
Subject [jira] [Created] (HIVE-15110) JDBC standalone jar is missing classes from hadoop-commons jar.
Date Wed, 02 Nov 2016 04:50:58 GMT
Gary Gregory created HIVE-15110:

             Summary: JDBC standalone jar is missing classes from hadoop-commons jar.
                 Key: HIVE-15110
             Project: Hive
          Issue Type: Bug
          Components: JDBC
    Affects Versions: 2.1.0, 2.0.0
         Environment: JBoss Developer Studio

Version: 9.1.0.GA
Build id: GA-v20160414-0124-B497
Build date: 20160414-0124

Oracle jdk1.8.0_91
            Reporter: Gary Gregory

- Create a Generic JDBC Driver in Eclipse DTP or JBoss Dev Studio.
- Connect to a Hive server.
- You get the error: 
java.lang.NoClassDefFoundError: org/apache/hadoop/conf/Configuration
	at org.apache.hive.jdbc.HiveConnection.createUnderlyingTransport(
	at org.apache.hive.jdbc.HiveConnection.createBinaryTransport(
	at org.apache.hive.jdbc.HiveConnection.openTransport(
	at org.apache.hive.jdbc.HiveConnection.<init>(
	at org.apache.hive.jdbc.HiveDriver.connect(
	at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(
	at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(
	at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnectionFactory.createConnection(
	at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(
	at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(
	at org.eclipse.datatools.connectivity.internal.ManagedConnection.createConnection(
Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.conf.Configuration
	at java.lang.ClassLoader.loadClass(
	at java.lang.ClassLoader.loadClass(
	... 15 more

For 2.0.0, I exploded the standalone jar, added the contents of hadoop-common-2.7.2.jar, and
repacked the jar. That works.

Please fix this as I do not want to do this for all new versions. I have to do this nonesense
because one of the runtime containers I deal with only deals with JDBC drivers that are all
in one jar.

This message was sent by Atlassian JIRA

View raw message