[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628691#action_12628691
]
dhruba borthakur commented on HADOOP-4044:
------------------------------------------
After a discussion with Joydeep, we came up with the idea that that
FileSystem.open() will transparently resolve a symbolic link if the symbolic
link is a relative or if it is of the form hdfs://bar/foo.txt. This means that
a HDFS symbolic link can point only to other hdfs pathnames.
In future, if the symbolic link is of the form file://dir/foo.txt, then the
FileSystem API can return it to higher layers for interpretation. This will
allow an HDFS symbolic link to refer to a pathname that is not a HDFS pathname.
I do not plan to implement this feature in the short term.
> 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
>
> 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.
