hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rushabh S Shah (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12379) NameNode getListing should use FileStatus instead of HdfsFileStatus
Date Thu, 31 Aug 2017 15:55:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-12379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149161#comment-16149161

Rushabh S Shah commented on HDFS-12379:

Mover#processPaths calls {{dfs#listPaths(fullPath, lastReturnedName, true)}} which uses storagepolicy
to make _move decisions_ which are not part of FileStatus object.
Maybe we can create another api which returns HdfsFileStatus and make mover use that api ?

> NameNode getListing should use FileStatus instead of HdfsFileStatus
> -------------------------------------------------------------------
>                 Key: HDFS-12379
>                 URL: https://issues.apache.org/jira/browse/HDFS-12379
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Zhe Zhang
> The public {{listStatus}} APIs in {{FileSystem}} and {{DistributedFileSystem}} expose
{{FileStatus}} instead of {{HdfsFileStatus}}. Therefore it is a waste to create the more expensive
{{HdfsFileStatus}} objects on NameNode.
> It should be a simple change similar to HDFS-11641. Marking incompatible because wire
protocol is incompatible. Not sure what downstream apps are affected by this incompatibility.
Maybe those directly using curl, or writing their own HDFS client.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message