hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4691) Disallow .reserved path component, given that HDFS-4434 does not allow /.reserved
Date Sun, 14 Apr 2013 17:32:16 GMT

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

Steve Loughran commented on HDFS-4691:

# it may be best to lay down a set of paths that are guaranteed to be forbidden, e.g. everything
starting with .dfs, that stops us having to expand the list of forbidden filenames later -and
so increase the risk of things breaking.
# it could be useful if you could enquire of the FS the list of forbidden paths. I believe
Windows doesn't let you create files called: {{COM1..COMn, LPT1..LPTn}} in any dir; Unices
usually block {{/dev}}. That could just be something declared as test metadata, metadata we'd
use in the tests to verify that the filesystems were telling the truth.
# Is a specific exception raised? If so we could expand that filesystem spec to say "all filesystems
MAY have a set of reserved filenames and directories, to which you MUST not write. If a user
attempts to write to a reserved path, the FS MUST thrown an {{IOException}}, which SHOULD
be {{ReservedPathException}}
> Disallow .reserved path component, given that HDFS-4434 does not allow /.reserved
> ---------------------------------------------------------------------------------
>                 Key: HDFS-4691
>                 URL: https://issues.apache.org/jira/browse/HDFS-4691
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Sanjay Radia

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message