hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12379) NameNode getListing should use FileStatus instead of HdfsFileStatus
Date Fri, 01 Sep 2017 00:56:00 GMT

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

Andrew Wang commented on HDFS-12379:

I'm -1 on any change that breaks wire compatibility. Is that what is being proposed here?

> 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