[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637651#action_12637651
]
Raghu Angadi commented on HADOOP-4044:
--------------------------------------
> I don't think anyone would argue that the values of isLink() and
> getLinkTarget()
Yes. It is of course proper data for 'stat' or FileStatus.
> But we don't want to make this many calls to our FS implementations, since
> they're RPCs. So, for performance,
so.. this is a performance compromise. But the arguments till now have been
about "perfect" api/implementation for a clearly imperfect/compromise (but well
performing) solution.
> Why does this suddenly make the that same data non-normal?
in the patch it is not clalled 'nextLinkOrOpenImpl()'.. it is just called
'openImpl()'.
> 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.
