Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8A20BDBB8 for ; Fri, 26 Oct 2012 23:33:13 +0000 (UTC) Received: (qmail 32032 invoked by uid 500); 26 Oct 2012 23:33:12 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 31919 invoked by uid 500); 26 Oct 2012 23:33:12 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 31824 invoked by uid 99); 26 Oct 2012 23:33:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Oct 2012 23:33:12 +0000 Date: Fri, 26 Oct 2012 23:33:12 +0000 (UTC) From: "Tsz Wo (Nicholas), SZE (JIRA)" To: hdfs-dev@hadoop.apache.org Message-ID: <2114623729.34035.1351294392559.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (HDFS-4118) Change INodeDirectory.getExistingPathINodes(..) to work with snapshots 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-4118: -------------------------------------------- Summary: Change INodeDirectory.getExistingPathINodes(..) to work with snapshots Key: HDFS-4118 URL: https://issues.apache.org/jira/browse/HDFS-4118 Project: Hadoop HDFS Issue Type: Sub-task Components: name-node Reporter: Tsz Wo (Nicholas), SZE Assignee: Jing Zhao {code} int getExistingPathINodes(byte[][] components, INode[] existing, boolean resolveLink) {code} The INodeDirectory above retrieves existing INodes from the given path components. It needs to be updated in order to understand snapshot paths. -- 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