You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Sangjin Lee (JIRA)" <ji...@apache.org> on 2015/01/08 22:24:35 UTC

[jira] [Commented] (HADOOP-11470) Remove some uses of obsolete guava APIs from the hadoop codebase

    [ https://issues.apache.org/jira/browse/HADOOP-11470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270067#comment-14270067 ] 

Sangjin Lee commented on HADOOP-11470:
--------------------------------------

Thanks [~cmccabe]. It is certainly true that the code will build cleanly with guava 16+. Running correctly with newer guava is of course predicated on the assumption that the compatible parts of guava behave in the same way, which I haven't verified.

> Remove some uses of obsolete guava APIs from the hadoop codebase
> ----------------------------------------------------------------
>
>                 Key: HADOOP-11470
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11470
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>         Attachments: HADOOP-11470.001.patch
>
>
> Along the same vein as HADOOP-11286, there are now several remaining usages of guava APIs that are now incompatible with a more recent version (e.g. 16).
> This JIRA proposes eliminating those usages. With this, the hadoop code base should run/compile cleanly even if guava 16 is used for example.
> This JIRA doesn't propose upgrading the guava dependency version however (just making the codebase compatible with guava 16+).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)