[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-4044:
-------------------------------------
Attachment: symLink6.patch
Hi Doug, thanks for your comments. I made all the changes you suggested except
one. Please let me know if these changes look good. I am working on another
unit test for this feature.
You had suggested that fs/spi/VfsStatusBase be renamed to FSLink. However, my
thinking is that the VfsStatusBase can be used not only for links but for other
items too. For example, if we want to return other types of NameNode exceptions
to the client, we could use VfsStatusBase. That's the reason why I am hesitant
to rename it to FSLink.
> 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, symLink1.patch, symLink4.patch,
> symLink5.patch, symLink6.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.
