[
https://issues.apache.org/jira/browse/HADOOP-11347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566578#comment-14566578
]
Hadoop QA commented on HADOOP-11347:
------------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 16m 23s | Pre-patch trunk compilation is
healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:green}+1{color} | tests included | 0m 0s | The patch appears to
include 1 new or modified test files. |
| {color:green}+1{color} | javac | 7m 34s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 9m 39s | There were no new javadoc
warning messages. |
| {color:green}+1{color} | release audit | 0m 22s | The applied patch does
not increase the total number of release audit warnings. |
| {color:red}-1{color} | checkstyle | 1m 5s | The applied patch generated 1
new checkstyle issues (total was 22, now 23). |
| {color:red}-1{color} | whitespace | 0m 0s | The patch has 1 line(s) that
end in whitespace. Use git apply --whitespace=fix. |
| {color:green}+1{color} | install | 1m 37s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 32s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 1m 51s | The patch does not introduce
any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | common tests | 22m 33s | Tests passed in
hadoop-common. |
| | | 61m 39s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12736428/HADOOP-11347.04.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / da05361 |
| checkstyle |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6882/artifact/patchprocess/diffcheckstylehadoop-common.txt
|
| whitespace |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6882/artifact/patchprocess/whitespace.txt
|
| hadoop-common test log |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6882/artifact/patchprocess/testrun_hadoop-common.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6882/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf901.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6882/console |
This message was 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
> Affects Versions: 2.7.0
> Reporter: Chris Nauroth
> Assignee: Varun Saxena
> Labels: BB2015-05-RFC
> Attachments: HADOOP-11347.001.patch, HADOOP-11347.002.patch,
> HADOOP-11347.03.patch, HADOOP-11347.04.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)