Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <1735707584.10881265067139290.JavaMail.jira@brutus.apache.org>
Date: Mon, 1 Feb 2010 23:32:19 +0000 (UTC)
From: "Hairong Kuang (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: quoted-printable


    [ https://issues.apache.org/jira/browse/HDFS-245?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D128283=
32#action_12828332 ]=20

Hairong Kuang commented on HDFS-245:
------------------------------------

Eli, great work! A couple of more comments:
1. INodeSymlink extends INodeFile in your patch. Should it extend INode?
2. Should FSDirectory#mkdirs, rootDir.getExistingPathINodes(components, ino=
des, true) be rootDir.getExistingPathINodes(components, inodes, false)? Mkd=
irs does not need to resolve the symlink of the last component.
3. Your document does not discuss the symlink resolution of concat, setQuot=
o, and getContentSummary etc. Could you please add them?

> 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, sym=
link-25-hdfs.patch, symlink-26-hdfs.patch, symlink-26-hdfs.patch, symLink1.=
patch, symLink1.patch, symLink11.patch, symLink12.patch, symLink13.patch, s=
ymLink14.patch, symLink15.txt, symLink15.txt, symlink16-common.patch, symli=
nk16-hdfs.patch, symlink16-mr.patch, symlink17-common.txt, symlink17-hdfs.t=
xt, symlink18-common.txt, symlink19-common-delta.patch, symlink19-common.tx=
t, symlink19-common.txt, symlink19-hdfs-delta.patch, symlink19-hdfs.txt, sy=
mlink20-common.patch, symlink20-hdfs.patch, symlink21-common.patch, symlink=
21-hdfs.patch, symlink22-common.patch, symlink22-hdfs.patch, symlink23-comm=
on.patch, symlink23-hdfs.patch, symlink24-hdfs.patch, symlink27-hdfs.patch,=
 symlink28-hdfs.patch, symlink29-hdfs.patch, symlink29-hdfs.patch, symlink3=
0-hdfs.patch, symlink31-hdfs.patch, symlink33-hdfs.patch, symlink35-hdfs.pa=
tch, symLink4.patch, symLink5.patch, symLink6.patch, symLink8.patch, symLin=
k9.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 op=
erating directly on the target file. However, archiving utilities can handl=
e symbolic links specially and manipulate them directly.

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