[
https://issues.apache.org/jira/browse/HDFS-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939964#comment-13939964
]
Hadoop QA commented on HDFS-6099:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12635396/HDFS-6099.3.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}. 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 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-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6427//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6427//console
This message is automatically generated.
> HDFS file system limits not enforced on renames.
> ------------------------------------------------
>
> Key: HDFS-6099
> URL: https://issues.apache.org/jira/browse/HDFS-6099
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 2.3.0
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Fix For: 2.4.0
>
> Attachments: HDFS-6099.1.patch, HDFS-6099.2.patch, HDFS-6099.3.patch,
> HDFS-6099.4.patch, HDFS-6099.5.patch
>
>
> {{dfs.namenode.fs-limits.max-component-length}} and
> {{dfs.namenode.fs-limits.max-directory-items}} are not enforced on the
> destination path during rename operations. This means that it's still
> possible to create files that violate these limits.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
