[
https://issues.apache.org/jira/browse/HDFS-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918688#comment-13918688
]
Gera Shegalov commented on HDFS-6045:
-------------------------------------
bq. [~chris.douglas] mentioned on YARN-1771 "Symlinks might be awkward to
support, but that discussion is for a separate ticket. Do you have a JIRA ref?".
For simplicity, I think the semantics should return array corresponding to a
fully resolved path that does not contain any symlinks.
If f=/a/b/c/d/e/f and b is a symlink b->/tmp/x and e is symlink e->y
then the the returned array will correspond to /tmp/x/c/d/y/f
> A single RPC API: FileStatus[] getFileStatus(Path f) to get status of all
> path components.
> ------------------------------------------------------------------------------------------
>
> Key: HDFS-6045
> URL: https://issues.apache.org/jira/browse/HDFS-6045
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: hdfs-client, namenode
> Reporter: Gera Shegalov
>
> This comes up in YARN-1771/MAPREDUCE-4907 on the server/client side of PUBLIC
> Distributed Cache. The deeper the path the more beneficial is the feature.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
