[
https://issues.apache.org/jira/browse/HDFS-4559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13600430#comment-13600430
]
Andrew Wang commented on HDFS-4559:
-----------------------------------
Agree with Suresh and Alejandro above. FileSystem doesn't support symlinks at
the moment, so it shouldn't be exposed.
[~sureshms] I've looked into this a fair bit since I'm working on HADOOP-8040
(porting symlinks to FileSystem). Full-on symlink support is definitely messier
in FileSystem since we don't have the nice separation of
FileContext/AbstractFileSystem, but it's still possible as long as the
FileSystem subclasses are willing to do some work. I hope to have a patch up
this week or next.
As a meta point, I don't think any FileSystem subclasses besides
DistributedFileSystem support resolving symlinks (S3, FTP, ?), and getting
resolution even just within HDFS would make 95% of our users happy.
> WebHDFS does not allow resolution of Symlinks
> ---------------------------------------------
>
> Key: HDFS-4559
> URL: https://issues.apache.org/jira/browse/HDFS-4559
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.3-alpha
> Reporter: Plamen Jeliazkov
> Assignee: Plamen Jeliazkov
> Fix For: 3.0.0, 2.0.5-beta
>
>
> WebHDFS allows you to create symlinks via the CREATESYMLINK operation, but
> the GETFILEINFO operation specifically calls the getFileInfo() method of the
> NameNodeRpcServer which does not resolve symlinks.
> I propose adding a parameter to GETFILEINFO such that if true will call
> getFileLinkInfo() rather than getFileInfo() which will resolve any symlinks.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
