hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-6055) Change default configuration to limit file name length in HDFS
Date Mon, 10 Mar 2014 22:00:45 GMT

     [ https://issues.apache.org/jira/browse/HDFS-6055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chris Nauroth updated HDFS-6055:

    Release Note: The default configuration of HDFS now sets dfs.namenode.fs-limits.max-component-length
to 255 for improved interoperability with other file system implementations.  This limits
each component of a file system path to a maximum of 255 bytes in UTF-8 encoding.  Attempts
to create new files that violate this rule will fail with an error.  Existing files that violate
the rule are not effected.  Previously, dfs.namenode.fs-limits.max-component-length was set
to 0 (ignored).  If necessary, it is possible to set the value to 0 in the cluster's configuration
to restore the old behavior.

> 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

View raw message