Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 2325 invoked from network); 4 Sep 2008 06:55:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Sep 2008 06:55:41 -0000 Received: (qmail 4373 invoked by uid 500); 4 Sep 2008 06:55:33 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 4348 invoked by uid 500); 4 Sep 2008 06:55:33 -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 4337 invoked by uid 99); 4 Sep 2008 06:55:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Sep 2008 23:55:33 -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; Thu, 04 Sep 2008 06:54:43 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 7EB19234C1CA for ; Wed, 3 Sep 2008 23:54:44 -0700 (PDT) Message-ID: <1354286138.1220511284517.JavaMail.jira@brutus> Date: Wed, 3 Sep 2008 23:54:44 -0700 (PDT) From: "dhruba borthakur (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=12628272#action_12628272 ] dhruba borthakur commented on HADOOP-4044: ------------------------------------------ The FileStatus object will indicate whether a path is a symbolic link. The NameNode will have a new INode type called INodeSymbolicLink. It will store the contents of the symbolic link in the INodeSymbolicLink object. This information will also be stored in the fsimage. The FileSystem.open() and FileSystem.create() calls will detect if the pathname is a symbolic link. If so, it transparently will open the path pointed to by the symbolic link. Symbolic links can be either relative or absolute. if the symbolic link is a complete URI, then nothign needs to be done. If it is a relative pathname, the dfs-client side code will invoke makeAbsolute to make it a full pathname. > 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 > > 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.