[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-4044:
-------------------------------------
Attachment: symLink14.patch
1. Performance testing: I have run DFSIOTest on 10 nodes only. I did not seen
any performance degradation for any operations, including creates, deletes,
reads or writes. I can re-run the test and post them here.
2. The problem is that the FileSystem.FSLinkResolver and FileSystem.resolve()
will become more complicated. Also, every operation in DFSClient will have to
convert a FsResultWritbale object into a FsResult object.
3. Fixed issues with FsResult constructor as you suggested.
4. I would like to remove the deprecated method DFSClient.getHints as part of a
separate JIRA.
> 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
> Fix For: 0.20.0
>
> Attachments: 4044_20081030spi.java, HADOOP-4044-strawman.patch,
> symLink1.patch, symLink1.patch, symLink11.patch, symLink12.patch,
> symLink13.patch, symLink14.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.
