[
https://issues.apache.org/jira/browse/HADOOP-11347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246121#comment-14246121
]
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/12687133/HADOOP-11347.001.patch
against trunk revision 25a0440.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:red}-1 findbugs{color}. The patch appears to introduce 3 new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common:
org.apache.hadoop.crypto.key.TestKeyProviderFactory
org.apache.hadoop.crypto.random.TestOsSecureRandom
org.apache.hadoop.fs.TestFilterFileSystem
org.apache.hadoop.security.alias.TestCredentialProviderFactory
org.apache.hadoop.fs.TestHarFileSystem
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5265//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5265//artifact/patchprocess/newPatchFindbugsWarningshadoop-common.html
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5265//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
> Fix For: 3.0.0
>
> Attachments: HADOOP-11347.001.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)
