[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638577#action_12638577
]
Doug Cutting commented on HADOOP-4044:
--------------------------------------
> clients are responsible to resolve links before using it
That might be a reasonable contract, but correct use of the API would then
involve extra RPCs to check links before trying to open them, no? But if it is
expected that folks will regularly pass unresolved links, then we shouldn't use
an exception, since callers of this method would be expected to immediately
handle the case of unresolved links. There's no need for a throw, as there
might be for, e.g., FileNotFound, which must be handled at some unknown layer
above. Exceptions are a long-distance goto, a control mechanism that should be
reserved for cases that require them, where the catcher is unknown.
> 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.
