Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 16 Apr 2015 22:02:59 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12821305.1429132018000.23357.1429221779352@Atlassian.JIRA>
In-Reply-To: <JIRA.12821305.1429132018000@Atlassian.JIRA>
References: <JIRA.12821305.1429132018000@Atlassian.JIRA>
 <JIRA.12821305.1429132018993@arcas>
Subject: [jira] [Commented] (HDFS-8153) Error Message points to wrong parent
 directory in case of path component name length error
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-8153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498822#comment-14498822 ] 

Hadoop QA commented on HDFS-8153:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12725698/hdfs-8153.001.patch
  against trunk revision 80a2a12.

    {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}.  There were no new javadoc 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 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-hdfs-project/hadoop-hdfs:

                  org.apache.hadoop.hdfs.TestEncryptionZonesWithKMS

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/10288//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/10288//console

This message is automatically generated.

> Error Message points to wrong parent directory in case of path component name length error
> ------------------------------------------------------------------------------------------
>
>                 Key: HDFS-8153
>                 URL: https://issues.apache.org/jira/browse/HDFS-8153
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.5.2
>            Reporter: Anu Engineer
>            Assignee: Anu Engineer
>         Attachments: hdfs-8153.001.patch
>
>
> If the name component length is greater than the permitted length, the error message points to wrong parent directory for mkdir and touchz.
> Here are examples where the parent directory name is in error message. In this example dfs.namenode.fs-limits.max-component-length is set to 19.
> {code}
> hdfs dfs -mkdir /user/hrt_qa/FileNameLength/really_big_name_dir01
> mkdir: The maximum path component name limit of really_big_name_dir01 in directory /user/hrt_qa/ is exceeded: limit=19 length=21
> {code}
> The expected value for the directory was _/user/hrt_qa/FileNameLength_. The same behavior is observed for touchz
> {code}
> hdfs dfs -touchz /user/hrt_qa/FileNameLength/really_big_name_0004
> touchz: The maximum path component name limit of really_big_name_0004 in directory /user/hrt_qa/ is exceeded: limit=19 length=20
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)