hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5104) Support dotdot name in NFS LOOKUP operation
Date Fri, 16 Aug 2013 21:53:48 GMT

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

Suresh Srinivas commented on HDFS-5104:

# Comment {{".." is only allowed in /.reserved/.inodes/... path}}, since you are talking ..
indicating remaining with path with trailing ... could be confusing. How about {{".." is allowed
in path starting with /.reserved/.inodes}}
# Hardcoded ".reserved" should use FSDirectory.DOT_RESERVED_STRING
# Hardcoded ".inodes" should use FSDirectory.DOT_INODES_STRING
# Please do cluster shutdown in try finally block in tests
# Please format the code correctly - while building testPath there is no space before and
after +
# How do you propose to handle if some passes {{/.reserved/.inodes/<root_inode>/..}}.
It should be an error condition right, instead of just returning the root?

> Support dotdot name in NFS LOOKUP operation
> -------------------------------------------
>                 Key: HDFS-5104
>                 URL: https://issues.apache.org/jira/browse/HDFS-5104
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: nfs
>    Affects Versions: 3.0.0
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>         Attachments: HDFS-5104.patch, HDFS-5104.patch.2
> Procedure LOOKUP searches a directory for a specific name and returns the file handle
for the corresponding file system object. NFS client sets filename as ".." to get the parent
directory information.
> Currently ".." is considered invalid name component. We only allow ".." when the path
is an inodeID path as "/.reserved/.inodes/.."

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