accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-804) Hadoop 2.0 Support
Date Tue, 26 Nov 2013 15:48:38 GMT


ASF subversion and git services commented on ACCUMULO-804:

Commit d5f16575f721d4fa7977dd1d1e8a9d9e7481b1ab in branch refs/heads/1.5.1-SNAPSHOT from [~busbey]
[;h=d5f1657 ]

ACCUMULO-804 fix the functional tests for hadoop-2.0

git-svn-id: 13f79535-47bb-0310-9956-ffa450edef68
(cherry picked from commit 17ef9c25ef2970b02b4771217f4bdf06fa0517a8)

Reason: Hadoop2 Compat
Author: Eric C. Newton
Ref: ACCUMULO-1792

Signed-off-by: Eric Newton <>

> Hadoop 2.0 Support
> ------------------
>                 Key: ACCUMULO-804
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.4.3
>            Reporter: Ed Kohlwey
>            Assignee: Eric Newton
>              Labels: hackathon
>             Fix For: 1.5.0
> We should start thinking about Hadoop 2 support now that it is Cloudera's recommended
distribution and many new Hadoop users will probably be adopting it.
> When I investigated this first a few months ago it seemed like the biggest barrier to
this was that all the Map/Reduce related tests are implemented using pseudo-private constructors
from Hadoop 1.0 that are no-longer present in Hadoop 2.0.
> The main strategy to fix this should probably be to adopt the Map/Reduce cluster test
object for testing the various Accumulo input formats instead of instrumenting them directly.
I have used this convenience object successfully on tests utilizing MockInstance, so I think
it should work fine.
> There may also be some filesystem API issues but I don't think they will be too severe.
> The other main issue is that we will need to actually deploy on Hadoop 1 and 2 and run
the integration tests once we start supporting both, so that will be a headache for release
testing that we should think through.

This message was sent by Atlassian JIRA

View raw message