[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638436#action_12638436
]
Doug Cutting commented on HADOOP-4044:
--------------------------------------
> we could define the API open(Path f) such that the parameter f is supposed to
> be a non-linked path.
Does calling something an "error" really make it an "error"? It seems like the
only motivation to call this an error is to justify using exceptions to handle
links, not that it would in fact be a user or program error to call it in this
way. Rather, it would be an expected, documented, supported event, but we'd
call it an error anyway, because otherwise we'd have to actually model the
functionality in our API.
> 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, 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.
