hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5818) Revert the renaming from checkSuperuserPrivilege to checkAccess by HADOOP-5643
Date Wed, 13 May 2009 18:37:45 GMT

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

Tsz Wo (Nicholas), SZE updated HADOOP-5818:
-------------------------------------------

        Assignee: Amar Kamat
    Hadoop Flags: [Reviewed]

+1  patch looks good.

> 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
>         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.


Mime
View raw message