Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 87640 invoked from network); 8 Sep 2008 18:22:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Sep 2008 18:22:07 -0000 Received: (qmail 45895 invoked by uid 500); 8 Sep 2008 18:22:02 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 45871 invoked by uid 500); 8 Sep 2008 18:22:02 -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 45860 invoked by uid 99); 8 Sep 2008 18:22:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Sep 2008 11:22:02 -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; Mon, 08 Sep 2008 18:21:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 494E1234C1D8 for ; Mon, 8 Sep 2008 11:21:44 -0700 (PDT) Message-ID: <1578598365.1220898104299.JavaMail.jira@brutus> Date: Mon, 8 Sep 2008 11:21: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=12629246#action_12629246 ] Doug Cutting commented on HADOOP-4044: -------------------------------------- I think a better API might be: {code} public FSDataInputStream open(Path f, int bufferSize) throws IOException { FileSystem fs = this; FileStatus stat = fs.getFileStatus(f); for (stat.isSymLink()) { f = stat.getSymLink(); fs = f.getFileSystem(getConf()); stat = fs.getStatus(f); } return fs.openData(stat, bufferSize); } public abstract FSDataInputStream openData(FileStatus stat, int bufferSize) throws IOException; {code} We could, for back-compatibility, have openData() default to calling open() for one release, but I think most if not all FileSystem implementations are included in Hadoop, so we're mostly concerned about client back-compatibilty here, not implementation back-compatibility. Also, FileStatus#getSymLink() should return a Path, not a String, no? > 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 > > > 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.