hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-4771) Remove the assumption that symlink is inside HDFS namespace and resolvable
Date Wed, 03 Jul 2013 19:22:20 GMT

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

Andrew Wang resolved HDFS-4771.

    Resolution: Not A Problem

Resolving this one for now, since I think the basic issue was fixed in HDFS-4765. Feel free
to reopen if you like.
> Remove the assumption that symlink is inside HDFS namespace and resolvable
> --------------------------------------------------------------------------
>                 Key: HDFS-4771
>                 URL: https://issues.apache.org/jira/browse/HDFS-4771
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Brandon Li
> Currently HDFS always resolves symlink when setting certain file attributes, such as
setPermission and setTime. And thus the client can't set some file attributes of the symlink
> Two major problems with current symlink support:
>  1. HDFS assumes the link is inside its own namespace. This is a problem when HDFS is
integrated into client's file system namespace.
> 2. Suppose the linked target is inside HFDS, HDFS doesn't really check whether the target
saved in the link file is a valid path. Even the target was valid, it could become invalid
as the namespace changes.
> For example, create a symlink /user/brandon/iamlink.lnk and it has the content(target)
as "/invalid/path". The file /user/brandon/iamlink.lnk can't be deleted since HDFS can't resolve

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