Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1819205045.1260510318185.JavaMail.jira@brutus>
Date: Fri, 11 Dec 2009 05:45:18 +0000 (UTC)
From: "Eli Collins (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6421) Symbolic links
In-Reply-To: <789869504.1260323298357.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-6421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789124#action_12789124 ] 

Eli Collins commented on HADOOP-6421:
-------------------------------------

By the way, I ended up shelling out to implement createSymlink, getLinkTarget and getFileLinkStatus. I also wrote an implementation that avoids this by making a NativeCall class that makes jni calls to {{link}},  {{readlink}} etc but integrating it into the native build was a pain. Does anyone know why all the auto-generated build files are checked in to src/native? 

> Symbolic links
> --------------
>
>                 Key: HADOOP-6421
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6421
>             Project: Hadoop Common
>          Issue Type: New Feature
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>         Attachments: symlink-25-common.patch, symlink24-common.patch
>
>
> Here's a jira for the common parts of HDFS-245, mostly changes to FileContext and AbstractFileSystem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.