Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2E2BDCAD3 for ; Thu, 3 May 2012 21:23:14 +0000 (UTC) Received: (qmail 81590 invoked by uid 500); 3 May 2012 21:23:13 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 81534 invoked by uid 500); 3 May 2012 21:23:13 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 81446 invoked by uid 99); 3 May 2012 21:23:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2012 21:23:13 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 May 2012 21:23:11 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 7C1B042E4DC for ; Thu, 3 May 2012 21:22:50 +0000 (UTC) Date: Thu, 3 May 2012 21:22:50 +0000 (UTC) From: "Tsz Wo (Nicholas), SZE (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <2133465212.23831.1336080170509.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <600488530.22367.1336060850562.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-3363) blockmanagement should stop using INodeFile & INodeFileUC MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267806#comment-13267806 ] Tsz Wo (Nicholas), SZE commented on HDFS-3363: ---------------------------------------------- - BlockCollection and MutableBlockCollection should be in the blockmanagement package. Then, services other than namenode can use them. Also, the javadoc should not use the term "file". - Remove BlockCollection.isDirectory() and the assert statement in BlockManager.getReplication(Block block). - Remove BlockCollection.isUnderConstruction() and replace the use of it in blockmanagement by checking instanceof MutableBlockCollection. - Rename getFullPathName() to getName(). It is the name of the collection but not necessarily a path name. - I agree with Daryn that we should rename BlocksMap.getINode(..) and, in addition, the local variable names such as fileInode. We could do the rename separately. > blockmanagement should stop using INodeFile & INodeFileUC > ---------------------------------------------------------- > > Key: HDFS-3363 > URL: https://issues.apache.org/jira/browse/HDFS-3363 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node > Affects Versions: 2.0.0, 3.0.0 > Reporter: John George > Assignee: John George > Priority: Minor > Attachments: HDFS-3363.java > > > Blockmanagement should stop using INodeFile and INodeFileUnderConstruction. One way would be to create an interface, like BlockColletion, that is passed along to the blockmanagement. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira