[
https://issues.apache.org/jira/browse/HIVE-22126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044382#comment-17044382
]
Eugene Chung commented on HIVE-22126:
-------------------------------------
[~dlavati] Shading guava for Hive also requires shading calcite modules. And it
leads to changing the FQCN of calcite-avatica JDBC driver. e.g.
* org.apache.calcite.jdbc.Driver ->
org.apache.hive.org.apache.calcite.jdbc.Driver
I stopped there cause I was not sure it's okay to change it.
If changing the name of driver is just internal or test concern, I think it's
okay.
I have some free time these days, so I am going to investigate this again.
> hive-exec packaging should shade guava
> --------------------------------------
>
> Key: HIVE-22126
> URL: https://issues.apache.org/jira/browse/HIVE-22126
> Project: Hive
> Issue Type: Bug
> Reporter: Vihang Karajgaonkar
> Assignee: Eugene Chung
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-22126.01.patch, HIVE-22126.02.patch,
> HIVE-22126.03.patch
>
>
> The ql/pom.xml includes complete guava library into hive-exec.jar
> https://github.com/apache/hive/blob/master/ql/pom.xml#L990 This causes a
> problems for downstream clients of hive which have hive-exec.jar in their
> classpath since they are pinned to the same guava version as that of hive.
> We should shade guava classes so that other components which depend on
> hive-exec can independently use a different version of guava as needed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
