hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11347) Inconsistent enforcement of umask between FileSystem and FileContext interacting with local file system.
Date Mon, 02 Mar 2015 16:51:05 GMT

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

Hadoop QA commented on HADOOP-11347:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12687146/HADOOP-11347.002.patch
  against trunk revision ca1c00b.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5812//console

This message is automatically generated.

> Inconsistent enforcement of umask between FileSystem and FileContext interacting with
local file system.
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-11347
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11347
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>            Reporter: Chris Nauroth
>            Assignee: Varun Saxena
>         Attachments: HADOOP-11347.001.patch, HADOOP-11347.002.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
(v6.3.4#6332)

Mime
View raw message