[jira] [Commented] (HDFS-12379) NameNode getListing should use FileStatus instead of HdfsFileStatus

["Shilun Fan (Jira)" <ji...@apache.org>]

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

Shilun Fan commented on HDFS-12379:
-----------------------------------

Bulk update: moved all 3.4.0 non-blocker issues, please move back if it is a blocker.


> 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
>            Priority: Major
>
> 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
(v8.20.10#820010)

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