Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <172419995.1253763796128.JavaMail.jira@brutus>
Date: Wed, 23 Sep 2009 20:43:16 -0700 (PDT)
From: "Nigel Daley (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-245) Create symbolic links in HDFS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nigel Daley commented on HDFS-245:
----------------------------------

Thanks Eli.  The design states:
{quote}
Loops should be avoided by having the client limit the number of links it will traverse
{quote}
What about loops within a filesystem?  Does the NN also limit the number of links it will traverse? 

You give examples of commands the operate on the link and examples that operate on the link target and examples of those that depend on a trailing slash.  Given this is a design, can you be explicitly and enumerate the commands for each of there?  For instance, setReplication, setTimes, du, etc.

What is the new options for fsck to report dangling links?  What does the output look like?

What is the new option for distcp to follow symlinks?  

If distcp doesn't follow symlinks, I assume it just copies the symlink.  In this case, is the symlink adjusted to point to the source location on the source FS?

What does the ls output look like for a symlink?

Do symlinks contribute bytes toward a quota?


> Create symbolic links in HDFS
> -----------------------------
>
>                 Key: HDFS-245
>                 URL: https://issues.apache.org/jira/browse/HDFS-245
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: 4044_20081030spi.java, designdocv1.txt, HADOOP-4044-strawman.patch, symlink-0.20.0.patch, symLink1.patch, symLink1.patch, symLink11.patch, symLink12.patch, symLink13.patch, symLink14.patch, symLink15.txt, symLink15.txt, symlink16-common.patch, symlink16-hdfs.patch, symlink16-mr.patch, symLink4.patch, symLink5.patch, symLink6.patch, symLink8.patch, symLink9.patch
>
>
> HDFS should support symbolic links. A symbolic link is a special type of file that contains a reference to another file or directory in the form of an absolute or relative path and that affects pathname resolution. Programs which read or write to files named by a symbolic link will behave as if operating directly on the target file. However, archiving utilities can handle symbolic links specially and manipulate them directly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.