Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-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 9A3E7100CB for ; Fri, 22 Nov 2013 09:28:53 +0000 (UTC) Received: (qmail 16785 invoked by uid 500); 22 Nov 2013 09:28:46 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 16525 invoked by uid 500); 22 Nov 2013 09:28:41 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 16402 invoked by uid 99); 22 Nov 2013 09:28:37 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Nov 2013 09:28:37 +0000 Date: Fri, 22 Nov 2013 09:28:37 +0000 (UTC) From: "Hadoop QA (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-9723) Improve error message when hadoop archive output path already exists 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/HADOOP-9723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829822#comment-13829822 ] Hadoop QA commented on HADOOP-9723: ----------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12615287/HADOOP-9723.2.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-tools/hadoop-archives. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3309//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3309//console This message is automatically generated. > Improve error message when hadoop archive output path already exists > -------------------------------------------------------------------- > > Key: HADOOP-9723 > URL: https://issues.apache.org/jira/browse/HADOOP-9723 > Project: Hadoop Common > Issue Type: Improvement > Affects Versions: 3.0.0, 2.0.4-alpha > Reporter: Stephen Chu > Assignee: Akira AJISAKA > Priority: Trivial > Attachments: HADOOP-9723.2.patch, HADOOP-9723.patch > > > When creating a hadoop archive and specifying an output path of an already existing file, we get an "Invalid Output" error message. > {code} > [schu@hdfs-vanilla-1 ~]$ hadoop archive -archiveName foo.har -p /user/schu testDir1 /user/schu > Invalid Output: /user/schu/foo.har > {code} > This error can be improved to tell users immediately that the output path already exists. -- This message was sent by Atlassian JIRA (v6.1#6144)