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

Hudson commented on ACCUMULO-804:
---------------------------------

Integrated in Accumulo-1.5 #76 (See 
[https://builds.apache.org/job/Accumulo-1.5/76/])
    ACCUMULO-804: start-dfs.sh is in a different place in hadoop-2 (Revision 
1467401)

     Result = SUCCESS
ecn : 
Files : 
* /accumulo/branches/1.5/test/system/continuous/agitator.pl

                
> 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.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 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

Reply via email to