hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-11470) eliminate use of incompatible guava APIs from the hadoop codebase
Date Thu, 08 Jan 2015 20:22:35 GMT

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

Sangjin Lee updated HADOOP-11470:
    Attachment: HADOOP-11470.001.patch

Patch posted. It's two APIs: Ranges and NullOutputStream. NullOutputStream is replaced by
hadoop's own IOUtils.NullOutputStream. Ranges is replaced by Apache Commons' LongRange.

For easier diff, see https://github.com/sjlee/hadoop/commit/636a2b534d6125bb92267f144d873792d4583b23

> eliminate use of incompatible 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

View raw message