[
https://issues.apache.org/jira/browse/HADOOP-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637318#action_12637318
]
Doug Cutting commented on HADOOP-4044:
--------------------------------------
> BTW Do you find such use of exceptions to be acceptable inside the name node?
No.
I thought I made it clear that I had not reviewed the namenode code changes,
but only those in the public APIs.
> No one is suggesting that we handle it as a single call
Linux's VFS does not handle both open and isLink in a single call, the way we'd
like to.
> I am interpreting your reference URL link differently - I am reading it and
> seeing that using exceptions for recovery is acceptable.
That's a separate issue. Recovery from an unexpected condition out of the
control of the code in question. That's not the case here. Links are an
expected, normal condition.
> 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.
