Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D6070ED8F for ; Tue, 19 Mar 2013 16:19:15 +0000 (UTC) Received: (qmail 14611 invoked by uid 500); 19 Mar 2013 16:19:15 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 14584 invoked by uid 500); 19 Mar 2013 16:19:15 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 14575 invoked by uid 99); 19 Mar 2013 16:19:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Mar 2013 16:19:15 +0000 Date: Tue, 19 Mar 2013 16:19:15 +0000 (UTC) From: "Hudson (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-804) Hadoop 2.0 Support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606453#comment-13606453 ] Hudson commented on ACCUMULO-804: --------------------------------- Integrated in Accumulo-1.5-Hadoop-2.0 #38 (See [https://builds.apache.org/job/Accumulo-1.5-Hadoop-2.0/38/]) ACCUMULO-804 defend against FileNotFoundExceptions for hadoop-2.0 (Revision 1458344) Result = SUCCESS ecn : Files : * /accumulo/branches/1.5 * /accumulo/branches/1.5/assemble * /accumulo/branches/1.5/core * /accumulo/branches/1.5/core/src/main/java/org/apache/accumulo/core/client/ZooKeeperInstance.java * /accumulo/branches/1.5/core/src/main/java/org/apache/accumulo/core/util/shell/commands/ImportDirectoryCommand.java * /accumulo/branches/1.5/examples * /accumulo/branches/1.5/fate/src/main/java/org/apache/accumulo/fate/ZooStore.java * /accumulo/branches/1.5/fate/src/main/java/org/apache/accumulo/fate/zookeeper/ZooSession.java * /accumulo/branches/1.5/server * /accumulo/branches/1.5/server/src/main/java/org/apache/accumulo/server/gc/GarbageCollectWriteAheadLogs.java * /accumulo/branches/1.5/server/src/main/java/org/apache/accumulo/server/gc/SimpleGarbageCollector.java * /accumulo/branches/1.5/server/src/main/java/org/apache/accumulo/server/master/tableOps/BulkImport.java * /accumulo/branches/1.5/server/src/main/java/org/apache/accumulo/server/tabletserver/Tablet.java * /accumulo/branches/1.5/src > 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