Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 79672 invoked from network); 29 Jan 2010 21:38:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Jan 2010 21:38:06 -0000 Received: (qmail 12948 invoked by uid 500); 29 Jan 2010 21:38:04 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 12913 invoked by uid 500); 29 Jan 2010 21:38:04 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 12879 invoked by uid 99); 29 Jan 2010 21:38:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jan 2010 21:38:04 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jan 2010 21:38:00 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 82E0929A0044 for ; Fri, 29 Jan 2010 13:37:39 -0800 (PST) Message-ID: <501634335.139051264801059535.JavaMail.jira@brutus.apache.org> Date: Fri, 29 Jan 2010 21:37:39 +0000 (UTC) From: "Tsz Wo (Nicholas), SZE (JIRA)" 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-245?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D128065= 12#action_12806512 ]=20 Tsz Wo (Nicholas), SZE commented on HDFS-245: --------------------------------------------- You may already have it: I think we need tests for cycles and different fil= e system schemes, e.g. {noformat} hdfs://namenode/foo/link1 (a symlink pointing to s3://hostname/bar) s3://hostname/bar/link2 (a symlink pointing to hdfs://namenode/foo) {noformat} Then, test various commands like ls, cp, distcp, etc. > 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, symLink4.patch, s= ymLink5.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 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.