accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-2017) Wikisearch should use Guava instead of Google Collections
Date Sat, 14 Dec 2013 08:05:06 GMT


Sean Busbey updated ACCUMULO-2017:

    Attachment: ACCUMULO-2017.1.patch.txt

Attached patch applies against new 1.4.5-SNAPSHOT branch from ACCUMULO-1977

> Wikisearch should use Guava instead of Google Collections
> ---------------------------------------------------------
>                 Key: ACCUMULO-2017
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: wikisearch
>    Affects Versions: 1.4.5, 1.5.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Critical
>             Fix For: 1.4.5, 1.5.1
>         Attachments: ACCUMULO-2017.1.patch.txt
> (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|] 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

View raw message