[
https://issues.apache.org/jira/browse/TEZ-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101991#comment-15101991
]
Hitesh Shah commented on TEZ-2164:
----------------------------------
The problem is due to module dependencies. If all tez modules are combined into
a single tez-assembly.jar at the very end, then relocation would work.
However, if tez-api is relocated and tez-dag say depends on tez-api, this will
create problems if any internal functions in tez-api use guava objects ( and
tez-dag tries to invoke such functions ) as tez-dag will be referring to
vanilla guava packages ( compile happens before relocation ) whereas tez-api
will only know about the relocated package location.
> Shade the guava version used by Tez and move to guava-18
> --------------------------------------------------------
>
> Key: TEZ-2164
> URL: https://issues.apache.org/jira/browse/TEZ-2164
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Hitesh Shah
> Priority: Critical
> Attachments: TEZ-2164.3.patch, TEZ-2164.4.patch,
> TEZ-2164.wip.2.patch, allow-guava-16.0.1.patch
>
>
> Should allow us to upgrade to a newer version without shipping a guava
> dependency.
> Would be good to do this in 0.7 so that we stop shipping guava as early as
> possible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
