Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Wed, 3 Jul 2013 19:22:20 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12645104.1367184073132.208012.1372879340160@arcas>
In-Reply-To: <JIRA.12645104.1367184073132@arcas>
References: <JIRA.12645104.1367184073132@arcas>
Subject: [jira] [Resolved] (HDFS-4771) Remove the assumption that symlink is
 inside HDFS namespace and resolvable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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 itself.
> 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 it.

--
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