Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 43478 invoked from network); 6 Oct 2008 16:40:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Oct 2008 16:40:47 -0000 Received: (qmail 44969 invoked by uid 500); 6 Oct 2008 16:40:43 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 44844 invoked by uid 500); 6 Oct 2008 16:40:42 -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 44833 invoked by uid 99); 6 Oct 2008 16:40:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Oct 2008 09:40:42 -0700 X-ASF-Spam-Status: No, hits=-1999.9 required=10.0 tests=ALL_TRUSTED,DNS_FROM_SECURITYSAGE,NORMAL_HTTP_TO_IP 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; Mon, 06 Oct 2008 16:39:38 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 59B88234C21D for ; Mon, 6 Oct 2008 09:39:44 -0700 (PDT) Message-ID: <1230360840.1223311184366.JavaMail.jira@brutus> Date: Mon, 6 Oct 2008 09:39:44 -0700 (PDT) From: "Doug Cutting (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=12637133#action_12637133 ] Doug Cutting commented on HADOOP-4044: -------------------------------------- Exceptions are intended for cases where you're not sure who will catch them. They're a non-local control-flow mechanism. Using them for normal control flow is an abuse and leads to spaghetti logic. In this case we are changing the FileSystem service-provider interface so that many methods can return either a link or a normal value. The appropriate implementation is a union result type, not exceptions. In Java we implement this union by extending a 'Linkable' base class. http://192.220.96.201/essays/java-style/exceptions.html http://www.javapractices.com/topic/TopicAction.do?Id=19 http://leepoint.net/notes-java/flow/exceptions/03exceptions.html > 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.