hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9552) Document types of permission checks performed for HDFS operations.
Date Wed, 16 Dec 2015 22:51:46 GMT

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

Chris Nauroth commented on HDFS-9552:
-------------------------------------

[~arpitagarwal], thank you for the review.

I think the concat entry as already written is accurate.  {{FSDirConcatOp#verifySrcFiles}}
contains this line:

{code}
        fsd.checkParentAccess(pc, iip, FsAction.WRITE); // for delete
{code}

I think the rationale is that since the original source files don't exist after the concat
completes, it's like a delete of those inodes, so it ought to enforce write on the parent
just like delete.

> Document types of permission checks performed for HDFS operations.
> ------------------------------------------------------------------
>
>                 Key: HDFS-9552
>                 URL: https://issues.apache.org/jira/browse/HDFS-9552
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HDFS-9552.001.patch, HDFS-9552.002.patch, hadoop-site.tar.bz2
>
>
> The HDFS permissions guide discusses our use of a POSIX-like model with read, write and
execute permissions associated with users, groups and the catch-all other class.  However,
there is no documentation that describes exactly what permission checks are performed by user-facing
HDFS operations.  This is a frequent source of questions, so it would be good to document
this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message