[
https://issues.apache.org/jira/browse/HDFS-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235197#comment-14235197
]
Hadoop QA commented on HDFS-7474:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12685198/HDFS-7474.000.patch
against trunk revision 7896815.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in
hadoop-hdfs-project/hadoop-hdfs
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/8918//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8918//console
This message is automatically generated.
> Avoid resolve path in FSPermissionChecker
> -----------------------------------------
>
> Key: HDFS-7474
> URL: https://issues.apache.org/jira/browse/HDFS-7474
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-7474.000.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)
