Return-Path: 
 <hdfs-issues-return-16312-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Received: (qmail 39639 invoked from network); 28 Mar 2011 19:03:45 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 28 Mar 2011 19:03:45 -0000
Received: (qmail 29618 invoked by uid 500); 28 Mar 2011 19:03:45 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 29498 invoked by uid 500); 28 Mar 2011 19:03:45 -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 29490 invoked by uid 99); 28 Mar 2011 19:03:45 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Mar 2011 19:03:45 +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; Mon, 28 Mar 2011 19:03:43 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id C26D0844B6
	for <hdfs-issues@hadoop.apache.org>; Mon, 28 Mar 2011 19:03:05 +0000 (UTC)
Date: Mon, 28 Mar 2011 19:03:05 +0000 (UTC)
From: "Tsz Wo (Nicholas), SZE (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <352847389.17264.1301338985793.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1217275313.11742.1301075526826.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1786) Some cli test cases expect a "null"
 message
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-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012176#comment-13012176 ] 

Tsz Wo (Nicholas), SZE commented on HDFS-1786:
----------------------------------------------

Hi Uma, since HADOOP-7174 was also committed to 0.21.1, could you provide a corresponding patch?  The current patch does not apply to 0.21.1.

> Some cli test cases expect a "null" message
> -------------------------------------------
>
>                 Key: HDFS-1786
>                 URL: https://issues.apache.org/jira/browse/HDFS-1786
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: test
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Uma Maheswara Rao G
>            Priority: Minor
>         Attachments: HDFS-1786.1.patch, HDFS-1786.patch
>
>
> There are a few tests cases specified in {{TestHDFSCLI}} and {{TestDFSShell}} expecting "null" messages.
> e.g. in {{testHDFSConf.xml}},
> {code}
>           <expected-output>get: null</expected-output>
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira