You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2009/05/14 22:29:46 UTC

[jira] Resolved: (HADOOP-5818) Revert the renaming from checkSuperuserPrivilege to checkAccess by HADOOP-5643

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

Tsz Wo (Nicholas), SZE resolved HADOOP-5818.
--------------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0

I have committed this.  Thanks, Amar!

> Revert the renaming from checkSuperuserPrivilege to checkAccess by HADOOP-5643
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5818
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5818
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Amar Kamat
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-5818-v1.0.patch
>
>
> HADOOP-5643 renamed FSNamesystem.checkSuperuserPrivilege to checkAccess.  However, "checkAccess" is confusing in FSNamesystem since there are other methods, checkPathAccess(..), checkParentAccess(..) and checkAncestorAccess(..) which have different meanings.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.