[
https://issues.apache.org/jira/browse/HDFS-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-7484:
----------------------------
Description: Currently {{FSDirectory#addLastINode}} takes an INodesInPath
instance, which uses null elements to indicate INodes to create, as its
parameter. This logic makes the logic of {{mkdir}} complicated. It will be
better to let {{addLastINode}}'s INodesInPath parameter only contain existing
INodes. (was: {{FSDirMkdirsOp#mkdirsRecursively()}} currently calculates the
permissions based on whether {{inheritPermission}} is true. This jira proposes
to simplify the workflow and make it explicit for the caller.)
> Make FSDirectory#addINode take existing INodes as its parameter
> ---------------------------------------------------------------
>
> Key: HDFS-7484
> URL: https://issues.apache.org/jira/browse/HDFS-7484
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Haohui Mai
> Assignee: Jing Zhao
> Attachments: HDFS-7484.000.patch, HDFS-7484.001.patch,
> HDFS-7484.002.patch, HDFS-7484.003.patch, HDFS-7484.004.patch,
> HDFS-7484.005.patch, HDFS-7484.006.patch, HDFS-7484.007.patch,
> HDFS-7484.008.patch
>
>
> Currently {{FSDirectory#addLastINode}} takes an INodesInPath instance, which
> uses null elements to indicate INodes to create, as its parameter. This logic
> makes the logic of {{mkdir}} complicated. It will be better to let
> {{addLastINode}}'s INodesInPath parameter only contain existing INodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
