[
https://issues.apache.org/jira/browse/HDFS-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930357#comment-13930357
]
Hudson commented on HDFS-6055:
------------------------------
SUCCESS: Integrated in Hadoop-Hdfs-trunk #1698 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1698/])
HDFS-6055. Change default configuration to limit file name length in HDFS.
Contributed by Chris Nauroth. (cnauroth:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1576095)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/fs/TestSymlinkHdfs.java
> Change default configuration to limit file name length in HDFS
> --------------------------------------------------------------
>
> Key: HDFS-6055
> URL: https://issues.apache.org/jira/browse/HDFS-6055
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Suresh Srinivas
> Assignee: Chris Nauroth
> Fix For: 3.0.0, 2.4.0
>
> Attachments: HDFS-6055.1.patch, HDFS-6055.2.patch
>
>
> Currently configuration "dfs.namenode.fs-limits.max-component-length" is set
> to 0. With this HDFS file names have no length limit. However, we see more
> users run into issues where they copy files from HDFS to another file system
> and the copy fails due to the file name length being too long.
> I propose changing the default configuration
> "dfs.namenode.fs-limits.max-component-length" to a reasonable value. This
> will be an incompatible change. However, user who need long file names can
> override this configuration to turn off length limit.
> What do folks think?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
