hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kanter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11347) RawLocalFileSystem#mkdir and create should honor umask
Date Wed, 17 Jun 2015 00:16:01 GMT

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

Robert Kanter commented on HADOOP-11347:

Looks like this broke a {{TestRollingLevelDBTimelineStore}}: YARN-3812

> RawLocalFileSystem#mkdir and create should honor umask
> ------------------------------------------------------
>                 Key: HADOOP-11347
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11347
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.7.0
>            Reporter: Chris Nauroth
>            Assignee: Varun Saxena
>              Labels: BB2015-05-RFC, incompatible
>             Fix For: 3.0.0
>         Attachments: HADOOP-11347.001.patch, HADOOP-11347.002.patch, HADOOP-11347.004.patch,
HADOOP-11347.03.patch, HADOOP-11347.05.patch
> The {{FileSystem}} and {{FileContext}} APIs are inconsistent in enforcement of umask
for newly created directories.  {{FileContext}} utilizes configuration property {{fs.permissions.umask-mode}}
and runs a separate {{chmod}} call to guarantee bypassing the process umask.  This is the
expected behavior for Hadoop as discussed in the documentation of {{fs.permissions.umask-mode}}.
 For the equivalent {{FileSystem}} APIs, it does not use {{fs.permissions.umask-mode}}.  Instead,
the permissions end up getting controlled by the process umask.

This message was sent by Atlassian JIRA

View raw message