[
https://issues.apache.org/jira/browse/HADOOP-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640518#action_12640518
]
Prasad Chakka commented on HADOOP-4332:
---------------------------------------
Yeah, we should catch if the correct driver doesn't exist. If we start adding
clients it might bloat the distribution with jars that not all of users may not
need.
> derbyclient.jar and derbytools.jar should be included in hive/lib
> -----------------------------------------------------------------
>
> Key: HADOOP-4332
> URL: https://issues.apache.org/jira/browse/HADOOP-4332
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/hive
> Environment: Cent OS 5 x86-64 JDK 1.6
> Reporter: Edward Capriolo
> Priority: Minor
>
> Attempting to use the Derby ClientDriver will cause a null pointer exception
> because derbyclient.jar and derbytools.jar are not in lib.
> hive> show tables;
> 08/10/02 15:17:12 INFO hive.metastore: Trying to connect to metastore
> with URI jdbc:derby://nyhadoop1:1527/metastore_db
> FAILED: Error in semantic analysis: java.lang.NullPointerException
> 08/10/02 15:17:12 ERROR ql.Driver: FAILED: Error in semantic analysis:
> java.lang.NullPointerException
> derbyclient.jar and derbytools.jar should probably be put in the hive/lib
> directory. Also this type of exception could happen often with different JDBC
> libraries the exception should be trapped better
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
