accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-804) Hadoop 2.0 Support
Date Thu, 11 Oct 2012 14:41:02 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474196#comment-13474196
] 

John Vines commented on ACCUMULO-804:
-------------------------------------

I really think this is something we should at least try to get into 1.5
                
> Hadoop 2.0 Support
> ------------------
>
>                 Key: ACCUMULO-804
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-804
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.5.0, 1.4.3
>            Reporter: Ed Kohlwey
>            Assignee: Billie Rinaldi
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message