Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 168C5200CE6 for ; Thu, 31 Aug 2017 17:55:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 133A616B5B4; Thu, 31 Aug 2017 15:55:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 59AA216B5B2 for ; Thu, 31 Aug 2017 17:55:09 +0200 (CEST) Received: (qmail 66589 invoked by uid 500); 31 Aug 2017 15:55:08 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 66572 invoked by uid 99); 31 Aug 2017 15:55:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Aug 2017 15:55:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 1B2CCC3478 for ; Thu, 31 Aug 2017 15:55:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id L8ntJfWxGGLt for ; Thu, 31 Aug 2017 15:55:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id B6C216125E for ; Thu, 31 Aug 2017 15:55:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 706BBE0E6E for ; Thu, 31 Aug 2017 15:55:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id AC69A2415D for ; Thu, 31 Aug 2017 15:55:00 +0000 (UTC) Date: Thu, 31 Aug 2017 15:55:00 +0000 (UTC) From: "Rushabh S Shah (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (HDFS-12379) NameNode getListing should use FileStatus instead of HdfsFileStatus MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 31 Aug 2017 15:55:10 -0000 [ https://issues.apache.org/jira/browse/HDFS-12379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149161#comment-16149161 ] Rushabh S Shah edited comment on HDFS-12379 at 8/31/17 3:54 PM: ---------------------------------------------------------------- {{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 ? was (Author: shahrs87): 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 (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org