hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7474) Avoid resolving path in FSPermissionChecker
Date Fri, 05 Dec 2014 22:24:13 GMT

     [ https://issues.apache.org/jira/browse/HDFS-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jing Zhao updated HDFS-7474:
       Resolution: Fixed
    Fix Version/s: 2.7.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

I've committed this to trunk and branch-2. Thanks Haohui for the review!

> Avoid resolving 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
>             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

View raw message