[
https://issues.apache.org/jira/browse/HIVE-18668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395629#comment-16395629
]
Sergey Shelukhin commented on HIVE-18668:
-----------------------------------------
Stopwatch is used in JvmPauseMonitor...
The list in the ql pom are actually the list of artifacts repackaged into the
big exec jar... it's a list of artifact IDs and groups, not packages. Doc at
https://maven.apache.org/plugins/maven-shade-plugin/examples/includes-excludes.html
{noformat}
<dependency>
<groupId>com.google.guava</groupId>
<artifactId>guava</artifactId>
<version>${guava.version}</version>
</dependency>
{noformat}
is the dependency in the same pom.
Before this patch com.google.common classes were in the exec jar, and after
they were not in exec jar...
So, in a Hive deployment in a container, where we only deploy the exec jar and
not the whole Hive lib, Hive picks up next available guava jar, usually Hadoop
or Tez; in our case it turned out to be 11 from Tez, that has incompatible
interface change.
> Really shade guava in ql
> ------------------------
>
> Key: HIVE-18668
> URL: https://issues.apache.org/jira/browse/HIVE-18668
> Project: Hive
> Issue Type: Bug
> Components: Druid integration
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HIVE-18668.01.patch
>
>
> After HIVE-15393 a test started to fail in druid; after some investigation it
> turned out that ql doesn't shade it's guava artifact at all...because it
> shades 'com.google.guava' instead 'com.google.common'
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
