[
https://issues.apache.org/jira/browse/HDFS-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HDFS-6099:
--------------------------------
Attachment: HDFS-6099.1.patch
The attached patch checks max path component length and max children during
renames. I reworked {{TestFsLimits}} quite a bit to do real file system
operations instead of directly accessing private {{FSDirectory}} methods. That
helped me write the new rename tests, and it also ends up covering more of the
real {{FSDirectory}} code.
> 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
> Attachments: HDFS-6099.1.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)
