accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ACCUMULO-2017) Wikisearch should use Guava instead of Google Collections
Date Sat, 14 Dec 2013 07:59:07 GMT
Sean Busbey created ACCUMULO-2017:
-------------------------------------

             Summary: Wikisearch should use Guava instead of Google Collections
                 Key: ACCUMULO-2017
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2017
             Project: Accumulo
          Issue Type: Sub-task
          Components: wikisearch
    Affects Versions: 1.5.0, 1.4.5
            Reporter: Sean Busbey
            Assignee: Sean Busbey
            Priority: Critical
             Fix For: 1.4.5, 1.5.1


(I'm using 1.5.0 as a placeholder or Wikisearch's master branch)

Wikisearch uses google collections 1.0, which has since been replaced by Guava.

Hadoop 2 relies on Guava for its internals and includes it in the classpath. The [Google Collections
decommissioning notice|https://code.google.com/p/google-collections/] warns

{quote}
Guava is a fully compatible superset of the old Google Collections Library. It also includes
years worth of bug fixes, doc fixes, and performance fixes, so we strongly encourage you to
use Guava instead of Google Collections.

If your application ever ends up with both google-collect-1.0.jar and guava-r##.jar on the
same classpath, simply remove the Google Collections JAR and you should be fine. If you don't
remove it, it will either cause terrible problems (if it comes before guava in the classpath)
or will never even be seen anyway (if it comes after).
{quote}

Under the Hadoop 2 profile, google collections comes first and a bunch of tests fail as a
result.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message