[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629609#action_12629609
]
Doug Cutting commented on HADOOP-4044:
--------------------------------------
> a symbolic link can occur during an open, create, chmod [ ... ] anywhere in
> the path.
Thanks for clarifying. I had not considered all of these cases.
> I am not suggesting that the FileSystem throws an exception, merely the NN
> throws that exception.
That's less of an issue, indeed.
> The problem is that we will need a similar object for all operations that
> involve a pathname: open, stat, chmod, rename, etc.
Could we use a common base class for the return value of all of these RPC
methods? The base class could have a "symLink" flag and fields that the client
could check. Is that better than exceptions?
> 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.
