[
https://issues.apache.org/jira/browse/HDFS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758043#action_12758043
]
Sanjay Radia commented on HDFS-245:
-----------------------------------
Konstantin> IV. Let the name-node throw MountPointException if the specified
path contains an external symlink. The client catches MountPointException,
calls a new method getLinkTarget() to resolve the link, and uses the resolved
path further to perform the action - open() a file.
Doug> I could live with this approach.
I can live with the MountPointException and 2nd call to get the link info.
Hard to believe that we did not find this middle ground earlier. So Doug you
*are* okay with using MountPoint exception as long as it does not return the
symlink info inside the exception?
Agree with Doug that getStatus() should suffice for the 2nd call.
> Create symbolic links in HDFS
> -----------------------------
>
> Key: HDFS-245
> URL: https://issues.apache.org/jira/browse/HDFS-245
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: dhruba borthakur
> Assignee: Eli Collins
> Attachments: 4044_20081030spi.java, HADOOP-4044-strawman.patch,
> symlink-0.20.0.patch, symLink1.patch, symLink1.patch, symLink11.patch,
> symLink12.patch, symLink13.patch, symLink14.patch, symLink15.txt,
> symLink15.txt, 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.
