[
https://issues.apache.org/jira/browse/HIVE-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641039#comment-13641039
]
Sushanth Sowmyan commented on HIVE-2055:
----------------------------------------
Hmm.. I agree with Ashutosh in that the length of the classpath is a valid
consideration, especially for Windows. For the HCat JsonSerDe as well, our
approach was to document that if you wanted it, users added the HCat jars to
HIVE_AUX_JARS_PATH, but not have that explicitly for all the tasks which don't
need it.
Adding it to HIVE_AUX_JARS_PATH will result in it getting appended to the
CLASSPATH for the job anyway, and people will get a long CLASSPATH, but that
won't affect people who aren't using hbase and need a shorter classpath because
they have other deps they want to add in.
I like the shorter deps idea, but I also agree that maintaining that from
hive's side is asking for desynch troubles later on. One possibility is that it
could be maintained on the hbase side, so that running "hbase
barebones-classpath" in a manner similar to the current "hbase classpath" can
return only the deps that would have otherwise been added by addDependencyJars
? Then, users could do something like:
{noformat}
HIVE_AUX_JARS_PATH = $(hbase barebones-classpath) hive -f hbase_query.q
{noformat}
> Hive HBase Integration issue
> ----------------------------
>
> Key: HIVE-2055
> URL: https://issues.apache.org/jira/browse/HIVE-2055
> Project: Hive
> Issue Type: Bug
> Components: HBase Handler
> Affects Versions: 0.10.0
> Reporter: sajith v
> Attachments:
> 0001-HIVE-2055-include-hbase-dependencies-in-launch-scrip.patch,
> HIVE-2055.patch
>
>
> Created an external table in hive , which points to the HBase table. When
> tried to query a column using the column name in select clause got the
> following exception : ( java.lang.ClassNotFoundException:
> org.apache.hadoop.hive.hbase.HiveHBaseTableInputFormat), errorCode:12,
> SQLState:42000)
--
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: http://www.atlassian.com/software/jira
