Return-Path: 
 <hdfs-issues-return-31535-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C9E669BF4
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Tue,  3 Jan 2012 16:45:24 +0000 (UTC)
Received: (qmail 30738 invoked by uid 500); 3 Jan 2012 16:45:24 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 30703 invoked by uid 500); 3 Jan 2012 16:45:24 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 30695 invoked by uid 99); 3 Jan 2012 16:45:24 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2012 16:45:24 +0000
X-ASF-Spam-Status: No, hits=-2001.6 required=5.0
	tests=ALL_TRUSTED,RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jan 2012 16:45:23 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 56B5C1364D0
	for <hdfs-issues@hadoop.apache.org>; Tue,  3 Jan 2012 16:44:39 +0000 (UTC)
Date: Tue, 3 Jan 2012 16:44:39 +0000 (UTC)
From: "Ivan Kelly (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1726335313.811.1325609079356.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <549011778.599.1325603319508.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2743) Streamline usage of bookkeeper
 journal manager
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/HDFS-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178808#comment-13178808 ] 

Ivan Kelly commented on HDFS-2743:
----------------------------------

{qoute}-1 tests included. The patch doesn't appear to include any new or modified tests.{quote}
Change is to packaging, no test required.

{quote}-1 javadoc. The javadoc tool appears to have generated 20 warning messages.
-1 findbugs. The patch appears to introduce 1 new Findbugs (version 1.3.9) warnings.
{quote}
This are not within the bkjournal contrib module.

{quote}
-1 release audit. The applied patch generated 1 release audit warnings (more than the trunk's current 0 warnings).
{quote}
This relates to: <br/>
 !????? /home/jenkins/jenkins-slave/workspace/PreCommit-HDFS-Build/trunk/hadoop-hdfs-project/hadoop-hdfs-httpfs/dev-support/findbugsExcludeFile.xml
                
> Streamline usage of bookkeeper journal manager
> ----------------------------------------------
>
>                 Key: HDFS-2743
>                 URL: https://issues.apache.org/jira/browse/HDFS-2743
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 0.24.0
>
>         Attachments: HDFS-2743.diff
>
>
> The current method of installing bkjournal manager involves generating a tarball, and extracting it with special flags over the hdfs distribution. This is cumbersome and prone to being broken by other changes (see https://svn.apache.org/repos/asf/hadoop/common/trunk@1220940). I think a cleaner way to doing this is to generate a single jar that can be placed in the lib dir of hdfs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira