You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Eli Collins (JIRA)" <ji...@apache.org> on 2009/12/16 05:25:18 UTC
[jira] Commented: (HDFS-245) Create symbolic links in HDFS
[ https://issues.apache.org/jira/browse/HDFS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791197#action_12791197 ]
Eli Collins commented on HDFS-245:
----------------------------------
Before I modified that path to take Doug's suggestion from HADOOP-6427 (the behavior for partially qualified targets) I wanted to get a +1 or two on the following symlink resolution behavior.
{noformat}
Given a symbolic link of the following form:
<----F---->
hdfs://host/A/B/link
<------P------>
If P points to P' then F' is the F part (scheme and host that identifies
a file system) of P'. If P is not a symlink then P' = P and F' = F.
Then link targets of the following type resolve as follows:
1. Fully qualified
<---------T--------->
hdfs://hostX/A/B/file <T> Fully qualified paths are simple.
2. Partially qualified (scheme but no host)
<--A--->
hdfs:///A/B/file <C><A> where C is the default file system of
the file context resolving the link, eg if
C = file:/// then <C><A> = file:///A/B/file
Think an NFS mount that links to /tmp.
3. Relative
<-T->
file <P'><T> eg if P resolves to hdfs://host1/XXX
then <P'><T> is hdfs://host1/YYY/file
4. Absolute
<---T--->
/A/B/file <F'><T>
eg if P = hdfs://host1/XXX
and P' = hdfs://host2/YYY
<F'><T> = hdfs://host2/A/B/file
{noformat}
> 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: Eli Collins
> Attachments: 4044_20081030spi.java, designdocv1.txt, designdocv2.txt, designdocv3.txt, HADOOP-4044-strawman.patch, symlink-0.20.0.patch, symlink-25-hdfs.patch, symlink-26-hdfs.patch, symlink-26-hdfs.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, symlink17-common.txt, symlink17-hdfs.txt, symlink18-common.txt, symlink19-common-delta.patch, symlink19-common.txt, symlink19-common.txt, symlink19-hdfs-delta.patch, symlink19-hdfs.txt, symlink20-common.patch, symlink20-hdfs.patch, symlink21-common.patch, symlink21-hdfs.patch, symlink22-common.patch, symlink22-hdfs.patch, symlink23-common.patch, symlink23-hdfs.patch, symlink24-hdfs.patch, symlink27-hdfs.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.