Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 74170 invoked from network); 10 Oct 2008 16:14:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Oct 2008 16:14:07 -0000 Received: (qmail 32883 invoked by uid 500); 10 Oct 2008 16:14:06 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 32235 invoked by uid 500); 10 Oct 2008 16:14:04 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 32220 invoked by uid 99); 10 Oct 2008 16:14:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Oct 2008 09:14:04 -0700 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, 10 Oct 2008 16:13:08 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6E591234C225 for ; Fri, 10 Oct 2008 09:13:44 -0700 (PDT) Message-ID: <542739708.1223655224451.JavaMail.jira@brutus> Date: Fri, 10 Oct 2008 09:13:44 -0700 (PDT) From: "Owen O'Malley (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-4044) Create symbolic links in HDFS In-Reply-To: <132525105.1219991324428.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638581#action_12638581 ] Owen O'Malley commented on HADOOP-4044: --------------------------------------- Ok, I realized after I posted that in fact the LinkResult is not abstract. Doug> do you think this logic is unique to HDFS? Well, currently yes, but in the long term hopefully not. In my proposal, most of the work would happen in LinkResult. Doug> Also, the pseudo code above will cause a stack overflow for a circular link. I was assuming (and included in the comments) that getNewPath would throw if it was too deeply nested. I would probably use a thread local variable to measure the depth of the traversal. It isn't great, but it would be encapsulated in LinkResult. > Create symbolic links in HDFS > ----------------------------- > > Key: HADOOP-4044 > URL: https://issues.apache.org/jira/browse/HADOOP-4044 > Project: Hadoop Core > Issue Type: New Feature > Components: dfs > Reporter: dhruba borthakur > Assignee: dhruba borthakur > Attachments: symLink1.patch, symLink1.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.