Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 23 Sep 2014 17:08:34 +0000 (UTC)
From: "Zhe Zhang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12742853.1411163081000.104597.1411492114347@Atlassian.JIRA>
In-Reply-To: <JIRA.12742853.1411163081000@Atlassian.JIRA>
References: <JIRA.12742853.1411163081000@Atlassian.JIRA>
 <JIRA.12742853.1411163081380@arcas>
Subject: [jira] [Updated] (HDFS-7104) Fix and clarify INodeInPath getter
 functions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HDFS-7104?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhe Zhang updated HDFS-7104:
----------------------------
    Status: Patch Available  (was: Open)

> Fix and clarify INodeInPath getter functions
> --------------------------------------------
>
>                 Key: HDFS-7104
>                 URL: https://issues.apache.org/jira/browse/HDFS-7104
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Zhe Zhang
>            Assignee: Zhe Zhang
>            Priority: Minor
>
> inodes is initialized with the number of patch components. After resolve,=
 it contains both non-null and null elements (introduced by dot-snapshot di=
rs).
> When getINodes is called, an array is returned excluding all non elements=
, which is the correct behavior. Meanwhile, the inodes array is trimmed too=
, which shouldn't be done by a getter.
> Because of the above, the behavior of getINodesInPath depends on whether =
getINodes has been called, which is not correct.
> The name of getLastINodeInPath is confusing =E2=80=93 it actually returns=
 the last non-null inode in the path. Also, shouldn't the return type be a =
single INode?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)