Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 94141 invoked from network); 17 Nov 2006 16:54:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Nov 2006 16:54:09 -0000 Received: (qmail 96000 invoked by uid 500); 17 Nov 2006 16:54:14 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 95818 invoked by uid 500); 17 Nov 2006 16:54:13 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 95755 invoked by uid 99); 17 Nov 2006 16:54:13 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Nov 2006 08:54:12 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Nov 2006 08:54:00 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7BF63714333 for ; Fri, 17 Nov 2006 08:53:40 -0800 (PST) Message-ID: <72960.1163782420503.JavaMail.jira@brutus> Date: Fri, 17 Nov 2006 08:53:40 -0800 (PST) From: "Christian Kunz (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Created: (HADOOP-733) dfs shell has inconsistent exit codes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org dfs shell has inconsistent exit codes ------------------------------------- Key: HADOOP-733 URL: http://issues.apache.org/jira/browse/HADOOP-733 Project: Hadoop Issue Type: Bug Components: dfs Affects Versions: 0.8.0 Reporter: Christian Kunz After upgrading to 0.8.0, some of my script applications stopped to work properly, seemingly because of hadoop dfs utility returning 0 exit code when it should not (kind of revival of hadoop-488, with a different cause). dfs -cat and dfs -rm always return exit code 0, even for non-existing files. The former can be traced back to the fact that DFSShell's 'run' method calls a 'doall' method without passing on the exit code ('doall' catches its own exceptions and returns an exit code). The latter occurs because the return code of the DFSClient delete method is only used in DFS Shell to print different messages without affecting exit code. There might be more inconsistent behavior of the dfs shell. Hadoop dfs command line should return 0 signaling success exactly when the corresponding unix command returns 0 (or at least it should be related to success whatever this means in a documented manner). I also would recommend to use a kind of regression test to prevent that this gets broken again. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira