hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-7040) HDFS dangerously uses @Beta methods from very old versions of Guava
Date Wed, 10 Sep 2014 21:53:34 GMT
Christopher Tubbs created HDFS-7040:

             Summary: HDFS dangerously uses @Beta methods from very old versions of Guava
                 Key: HDFS-7040
                 URL: https://issues.apache.org/jira/browse/HDFS-7040
             Project: Hadoop HDFS
          Issue Type: Bug
    Affects Versions: 2.4.1, 2.5.0, 2.4.0
            Reporter: Christopher Tubbs

HDFS uses LimitInputStream from Guava. This was introduced as @Beta and is risky for any application
to use.

The problem is further exacerbated by Hadoop's dependency on Guava version 11.0.2, which is
quite old for an active project (Feb. 2012).

Because Guava is very stable, projects which depend on Hadoop and use Guava themselves, can
use up through Guava version 14.x

However, in version 14, Guava deprecated LimitInputStream and provided a replacement. Because
they make no guarantees about compatibility about @Beta classes, they removed it in version

What should be done: Hadoop should updated its dependency on Guava to at least version 14
(currently Guava is on version 19). This should have little impact on users, because Guava
is so stable.

HDFS should then be patched to use the provided alternative to LimitInputStream, so that downstream
packagers, users, and application developers requiring more recent versions of Guava (to fix
bugs, to use new features, etc.) will be able to swap out the Guava dependency without breaking

Alternative: While Hadoop cannot predict the marking and removal of deprecated code, it can,
and should, avoid the use of @Beta classes and methods that do not offer guarantees. If the
dependency cannot be bumped, then it should be relatively trivial to provide an internal class
with the same functionality, that does not rely on the older version of Guava.

This message was sent by Atlassian JIRA

View raw message