Return-Path: 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 2E2A6669D for ; Thu, 9 Jun 2011 22:59:22 +0000 (UTC) Received: (qmail 22787 invoked by uid 500); 9 Jun 2011 22:59:22 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 22746 invoked by uid 500); 9 Jun 2011 22:59:22 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 22738 invoked by uid 99); 9 Jun 2011 22:59:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jun 2011 22:59:22 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_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; Thu, 09 Jun 2011 22:59:19 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id E4F8610B89E for ; Thu, 9 Jun 2011 22:58:58 +0000 (UTC) Date: Thu, 9 Jun 2011 22:58:58 +0000 (UTC) From: "Hadoop QA (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <2058529553.8982.1307660338934.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1331646687.66777.1307126147561.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-2030) Fix the usability of namenode upgrade command MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046896#comment-13046896 ] Hadoop QA commented on HDFS-2030: --------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12481981/HDFS-2030-3.patch against trunk revision 1134031. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 2 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these core unit tests: org.apache.hadoop.cli.TestHDFSCLI +1 contrib tests. The patch passed contrib unit tests. +1 system test framework. The patch passed system test framework compile. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/756//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HDFS-Build/756//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/756//console This message is automatically generated. > Fix the usability of namenode upgrade command > --------------------------------------------- > > Key: HDFS-2030 > URL: https://issues.apache.org/jira/browse/HDFS-2030 > Project: Hadoop HDFS > Issue Type: Bug > Affects Versions: 0.23.0 > Reporter: Bharath Mundlapudi > Assignee: Bharath Mundlapudi > Priority: Minor > Fix For: 0.23.0 > > Attachments: HDFS-2030-1.patch, HDFS-2030-2.patch, HDFS-2030-3.patch > > > Fixing the Namenode upgrade option along the same line as Namenode format option. > If clusterid is not given then clusterid will be automatically generated for the upgrade but if clusterid is given then it will be honored. > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira