[
https://issues.apache.org/jira/browse/HADOOP-11470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270060#comment-14270060
]
Colin Patrick McCabe commented on HADOOP-11470:
-----------------------------------------------
I have not verified that it allows running with a newer Guava, but the code
changes certainly look reasonable. +1, pending jenkins
bq. For easier diff, see
https://github.com/sjlee/hadoop/commit/636a2b534d6125bb92267f144d873792d4583b23
I use "git patch viewer" for Chrome, which makes all JIRA patches appear with
context.
https://chrome.google.com/webstore/detail/git-patch-viewer/hkoggakcdopbgnaeeidcmopfekipkleg
> 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
(v6.3.4#6332)
