[
https://issues.apache.org/jira/browse/HDFS-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791511#comment-13791511
]
Daryn Sharp commented on HDFS-5329:
-----------------------------------
The second patch doesn't include the first patch's change to return the path
component in the returned status? The new patch seems to expect {{startAfter}}
to now be a full path instead of just the path component? That's not right.
Could you elaborate on the actual bug you are seeing? The linked jira mentions
an issue with using inode paths, but passing back an inode path for the
directory and a start after path component appears like it should work fine.
> getFileInfo doesn't return file name
> ------------------------------------
>
> Key: HDFS-5329
> URL: https://issues.apache.org/jira/browse/HDFS-5329
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Reporter: Brandon Li
> Assignee: Brandon Li
> Attachments: HDFS-5329.1.patch, HDFS-5329.patch
>
>
> FSDirectory#getFileInfo() always returns empty string as the file name to the
> client.
> When the client is using inode path to get the file info, the client could
> also need the server to return the file name.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
