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 C427FD1C1 for ; Mon, 5 Nov 2012 03:34:16 +0000 (UTC) Received: (qmail 93499 invoked by uid 500); 5 Nov 2012 03:34:16 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 93429 invoked by uid 500); 5 Nov 2012 03:34:15 -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 93354 invoked by uid 99); 5 Nov 2012 03:34:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Nov 2012 03:34:12 +0000 Date: Mon, 5 Nov 2012 03:34:12 +0000 (UTC) From: "Tsz Wo (Nicholas), SZE (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <914870816.67358.1352086452613.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (HDFS-4151) Passing INodesInPath instead of INode[] in FSDirectory MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tsz Wo (Nicholas), SZE created HDFS-4151: -------------------------------------------- Summary: Passing INodesInPath instead of INode[] in FSDirectory Key: HDFS-4151 URL: https://issues.apache.org/jira/browse/HDFS-4151 Project: Hadoop HDFS Issue Type: Improvement Components: name-node Reporter: Tsz Wo (Nicholas), SZE Assignee: Tsz Wo (Nicholas), SZE Priority: Minor Currently, many methods in FSDirectory pass INode[] as a parameter. It is better to pass INodesInPath so that we can add more path information later on. This is especially useful in Snapshot implementation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira