[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629656#action_12629656
]
Robert Chansler commented on HADOOP-4044:
-----------------------------------------
Is there a presumption that if (as in Sanjay's example) /foo/bar is a link to
"X" that /foo/bar/zoo is exactly "X/zoo"? This might be problematic if X is a
reference to another system, introducing a requirement for interfaces
everywhere to have a "root" and "remaining" parameters. Or maybe as a practical
matter this is unimportant. In any case the rules need to be clear. Is X="/a/b"
different from X="/a/b/" when resolving /foo/bar/zoo? Are there cases where
"/foo/bar/zoo" is not permitted as a path on the local system, requiring that
path syntax checking be done late just in case /foo/bar is a link?
> 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
>
>
> 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.
