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 2FD80D40A for ; Mon, 11 Mar 2013 14:22:56 +0000 (UTC) Received: (qmail 74091 invoked by uid 500); 11 Mar 2013 14:21:36 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 69805 invoked by uid 500); 11 Mar 2013 14:21:25 -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 68820 invoked by uid 99); 11 Mar 2013 14:21:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Mar 2013 14:21:17 +0000 Date: Mon, 11 Mar 2013 14:21:16 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ACCUMULO-1169) Can't build against CDH3U5 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Josh Elser created ACCUMULO-1169: ------------------------------------ Summary: Can't build against CDH3U5 Key: ACCUMULO-1169 URL: https://issues.apache.org/jira/browse/ACCUMULO-1169 Project: Accumulo Issue Type: Improvement Components: tserver Affects Versions: 1.5.0 Environment: branch 1.5 Reporter: Josh Elser Assignee: Keith Turner Priority: Critical I tried to compile 1.5 against CDH3U5 recently and noticed that I could no longer do so due to a change in server/o.a.a.s.m.r.HadoopLogCloser. In CDH3U5, DistributedFileSystem#recoverLease(Path) throws IOException *and* NoSuchMethodException, whereas 0.20.205, 1.0.4, 1.1.0, and 2.0.3-ALPHA (I believe that was the list I checked; regardless, a large majority of Apache Hadoop releases). I believe we could do some reflection magic here to catch when the underlying DistributedFileSystem throws the additional exception, and thus know when we have to catch it. It would be nice to have this in for 1.5 to support customers who want to use CDH3, but I can understand objections to putting work-arounds in for non-Apache Hadoop versions. I'll also try to get a patch together today for this if no one beats me to it. -- 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