[
https://issues.apache.org/jira/browse/HADOOP-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297244#comment-14297244
]
Sangjin Lee commented on HADOOP-10101:
--------------------------------------
HADOOP-11286 replaced all use of guava's LimitInputStream with Hadoop's own. It
appears a new reference to guava's LimitInputStream has crept in since then.
Since we introduced Hadoop's LimitInputStream, we might as well stick with that
approach. I understand it is not perfect (as people can still introduce new
references without enforcement), but it still gives us value.
Could you fix that to use Hadoop's LimitInputStream rather than using
ByteStreams.limit()? That way it can be committed to branch-2 as well.
If we fix that one, then the compatibility is expanded to prior to 18.0,
correct?
> Update guava dependency to the latest version
> ---------------------------------------------
>
> Key: HADOOP-10101
> URL: https://issues.apache.org/jira/browse/HADOOP-10101
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.2.0, 2.6.0
> Reporter: Rakesh R
> Assignee: Vinayakumar B
> Attachments: HADOOP-10101-002.patch, HADOOP-10101-004.patch,
> HADOOP-10101-005.patch, HADOOP-10101-006.patch, HADOOP-10101-007.patch,
> HADOOP-10101.patch, HADOOP-10101.patch
>
>
> The existing guava version is 11.0.2 which is quite old. This
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
