[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638193#action_12638193
]
dhruba borthakur commented on HADOOP-4044:
------------------------------------------
>From my perspective, I am not buying (yet) Doug's argument of saying that
>not-throwing exceptions inside the namenode is a *better* programming style.
>If there is a proposal to change all internal namenode methods to return
>object-return-types instead of throwing UnresolvedPathException, then I am
>against it.
However, for the RPC interfaces, I like Doug's programming style of returning
object-as-return-types rather than throwing exceptions, especially in the case
of symbolic links.
> 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.
