[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637670#action_12637670
]
Doug Cutting commented on HADOOP-4044:
--------------------------------------
> I was only wondering why we are ok with compromise in one aspect and not
> about the other.
What compromise is this?
> it makes perfect sense. My objection has been calling it open() and returning
> link some times.
So it was all about the method name? Okay, then please suggest new method
names and return type names, rather than suggesting we use exceptions to return
normal data. I personally find the 'xOry' names useful in pseudo code, when
I'm trying to make a point, but a bit verbose in real code. We don't call
FileStatus NameAndModifiedDateAndOwnerAnd....
> This also allows HDFS to use exceptions since we don't want to change the
> names.
What? I don't follow your logic here. Why can't HDFS change method names?
> 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.
