[
https://issues.apache.org/jira/browse/HDFS-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Zhao updated HDFS-7474:
----------------------------
Issue Type: Sub-task (was: Improvement)
Parent: HDFS-7508
> Avoid resolving path in FSPermissionChecker
> -------------------------------------------
>
> Key: HDFS-7474
> URL: https://issues.apache.org/jira/browse/HDFS-7474
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Fix For: 2.7.0
>
> Attachments: HDFS-7474.000.patch, HDFS-7474.001.patch
>
>
> Currently for an typical namenode operation a path can be resolved multiple
> times. Usually the FSPermissionChecker first takes the path string as input
> and resolve the path before the real checking. After permission checking the
> path is then resolved again (and again) for real operations in FSNamesystem
> and FSDirectory. Ideally we should resolve the path only once, and use
> INodesInPath internally afterwards. As a first step, we can start from
> avoiding path resolving in FSPermissionChecker.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
