[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-4044:
-------------------------------------
Attachment: symLink12.patch
Incorporated Sanjay's review comments. The FileSystem.createSymLink() does take
two parameters, but only the first one needs to be "resolved". The second one
can be anything (just a blob) and does not need to be resolved. In fact, the
second parameter could be a dangling non-existent path.
Included test cases for all FileSystem APIs that were modified.
>From Rob''s list of tests
* Shell commands -- unit test included
* Trash -- unit test included (because Trash is a pure FileSystem client)
* Archives -- current implementation does not follow symbolic links.
* distcp -- pure FileSystem client, does not follow symbolic links
* chmod, chown, chgrp APIs -- unit test included
* Rename - unit test included
> 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: 4044_20081030spi.java, HADOOP-4044-strawman.patch,
> symLink1.patch, symLink1.patch, symLink11.patch, symLink12.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.
