hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7474) Avoid resolve path in FSPermissionChecker
Date Fri, 05 Dec 2014 07:37:12 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235225#comment-14235225

Hadoop QA commented on HDFS-7474:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against trunk revision 0653918.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8927//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

View raw message