tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hitesh Shah (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TEZ-2164) Shade the guava version used by Tez
Date Tue, 28 Jul 2015 20:35:04 GMT

     [ https://issues.apache.org/jira/browse/TEZ-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Hitesh Shah updated TEZ-2164:
    Attachment: TEZ-2164.wip.2.patch

Does not solve guava issue completely. 

wip.2 patch does the following:
   - introduce a new guava-tez module ( needs to be built separately )
   - guava-tez is basically the relocated classes of guava-18.0
   - all tez internals now depend on guava-tez 
   - hadoop still depends on guava-11 and it is still needed as one of the APIs exposed by
YARN uses guava in a templated class. 
   - hadoop depends on curator which uses guava in its apis too

Still to be done:
   - add a profile/flag to control whether guava ( from transitive dependencies of hadoop,
etc) is bundled in the tarballs or not. tez-guava will always be bundled. If not bundled,
the onus is on the user to provide a guava version compatible with hadoop's requirements for
the runtime to function correctly. The user can use tez.aux.uris to add the guava jar as needed.

> Shade the guava version used by Tez
> -----------------------------------
>                 Key: TEZ-2164
>                 URL: https://issues.apache.org/jira/browse/TEZ-2164
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Priority: Critical
>         Attachments: 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

View raw message