[
https://issues.apache.org/jira/browse/HIVE-25101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343018#comment-17343018
]
Istvan Toth commented on HIVE-25101:
------------------------------------
We could also solve the problem the other way around, by not adding the shaded
HBase libraries to the classpath, and standardizing on the unshaded libraries,
but I prefer this one due to the reasons above.
> Remove HBase libraries from Hive distribution
> ---------------------------------------------
>
> Key: HIVE-25101
> URL: https://issues.apache.org/jira/browse/HIVE-25101
> Project: Hive
> Issue Type: Improvement
> Components: HBase Handler, Hive
> Affects Versions: 4.0.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hive currently packages HBase libraries into its lib directory.
> It also adds the HBase libraries separately to its classpath in the hive
> startup script.
> Having both mechanisms is redundant, and it also causes errors, as the
> standard HBase libraries packaged into Hive are unshaded, while the libraries
> added by _hbase mapredcp_
> are shaded, and the two are NOT compatible when custom coprocessors are used,
> and in some cases the classpaths during local execution and for MR/TEZ jobs
> are mutually incompatible.
> I propose removing all HBase libraries from the distribution, and pulling
> them via the hbase mapredcp mechanism.
> This also solves the old problem of including ancient HBase alpha versions
> Hive.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
