[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816975#comment-16816975 ] Billie Rinaldi commented on MAPREDUCE-7010: --- [~boky01], good point. This patch solves a related problem we encountered but does not complete the task of allowing other users to access the files. This was not intended; apologies for not noticing it sooner. > Make Job History File Permissions configurable > -- > > Key: MAPREDUCE-7010 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7010 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Gergely Novák >Priority: Major > Fix For: 3.1.0 > > Attachments: MAPREDUCE-7010.001.patch, MAPREDUCE-7010.002.patch, > MAPREDUCE-7010.003.patch, MAPREDUCE-7010.004.patch > > > Currently the mapreduce job history files are written with 770 permissions > which can be accessed by job user or other user part of hadoop group. > There might be users who are not part of the hadoop group but want to access > these history files. We should provide ability to change the default > permissions for staging files. > The default should remain 770. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816694#comment-16816694 ] Andras Bokor commented on MAPREDUCE-7010: - [~billie.rinaldi], [~GergelyNovak], After checking the code change as far as I understand this ticket allows to set custom permission for other's on intermediate directory but not on the files inside the directory. I mean if I set 777 with the new property everybody will be able to list the directory but not read the files. Is it intended? A customer would like to start using this but I am not sure if that is the desired behavior. > Make Job History File Permissions configurable > -- > > Key: MAPREDUCE-7010 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7010 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Gergely Novák >Priority: Major > Fix For: 3.1.0 > > Attachments: MAPREDUCE-7010.001.patch, MAPREDUCE-7010.002.patch, > MAPREDUCE-7010.003.patch, MAPREDUCE-7010.004.patch > > > Currently the mapreduce job history files are written with 770 permissions > which can be accessed by job user or other user part of hadoop group. > There might be users who are not part of the hadoop group but want to access > these history files. We should provide ability to change the default > permissions for staging files. > The default should remain 770. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377747#comment-16377747 ] Hudson commented on MAPREDUCE-7010: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13719 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/13719/]) MAPREDUCE-7010. Make Job History File Permissions configurable. (billie: rev 7dd385098c7a3046e6b049e70669d5b726de79c9) * (edit) hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/jobhistory/JobHistoryEventHandler.java * (edit) hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/JobHistoryUtils.java * (edit) hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/JHAdminConfig.java * (edit) hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestJobHistoryUtils.java * (edit) hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml > Make Job History File Permissions configurable > -- > > Key: MAPREDUCE-7010 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7010 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Gergely Novák >Priority: Major > Fix For: 3.2.0 > > Attachments: MAPREDUCE-7010.001.patch, MAPREDUCE-7010.002.patch, > MAPREDUCE-7010.003.patch, MAPREDUCE-7010.004.patch > > > Currently the mapreduce job history files are written with 770 permissions > which can be accessed by job user or other user part of hadoop group. > There might be users who are not part of the hadoop group but want to access > these history files. We should provide ability to change the default > permissions for staging files. > The default should remain 770. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[
https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377365#comment-16377365
]
Hadoop QA commented on MAPREDUCE-7010:
--
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
13s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
8s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 15m
44s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
39s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
33s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
29s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
11m 37s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
6s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
5s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
9s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
38s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 32s{color} | {color:orange}
hadoop-mapreduce-project/hadoop-mapreduce-client: The patch generated 6 new +
377 unchanged - 1 fixed = 383 total (was 378) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
2s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
10m 31s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
55s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
47s{color} | {color:green} hadoop-mapreduce-client-core in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
51s{color} | {color:green} hadoop-mapreduce-client-common in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 9m
24s{color} | {color:green} hadoop-mapreduce-client-app in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 67m 7s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:5b98639 |
| JIRA Issue | MAPREDUCE-7010 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12912074/MAPREDUCE-7010.004.patch
|
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit shadedclient findbugs checkstyle xml |
| uname | Linux 3702e60066ed 4.4.0
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377264#comment-16377264 ] Billie Rinaldi commented on MAPREDUCE-7010: --- Thanks, [~GergelyNovak]! Patch #4 looks good to me. I plan to commit this to trunk after we get another clean precommit build. Is this patch targeted for any 2.x versions? > Make Job History File Permissions configurable > -- > > Key: MAPREDUCE-7010 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7010 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Gergely Novák >Priority: Major > Attachments: MAPREDUCE-7010.001.patch, MAPREDUCE-7010.002.patch, > MAPREDUCE-7010.003.patch, MAPREDUCE-7010.004.patch > > > Currently the mapreduce job history files are written with 770 permissions > which can be accessed by job user or other user part of hadoop group. > There might be users who are not part of the hadoop group but want to access > these history files. We should provide ability to change the default > permissions for staging files. > The default should remain 770. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377228#comment-16377228 ] Gergely Novák commented on MAPREDUCE-7010: -- I'm so sorry, I never intended to include that change to the patch, I made it only to run the test locally. Removed it from patch #4. > Make Job History File Permissions configurable > -- > > Key: MAPREDUCE-7010 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7010 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Gergely Novák >Priority: Major > Attachments: MAPREDUCE-7010.001.patch, MAPREDUCE-7010.002.patch, > MAPREDUCE-7010.003.patch, MAPREDUCE-7010.004.patch > > > Currently the mapreduce job history files are written with 770 permissions > which can be accessed by job user or other user part of hadoop group. > There might be users who are not part of the hadoop group but want to access > these history files. We should provide ability to change the default > permissions for staging files. > The default should remain 770. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377015#comment-16377015 ] Billie Rinaldi commented on MAPREDUCE-7010: --- The new unit test looks good. I don't think we should change the value of TEST_DIR because this "test.build.data" directory is supposed to be created and cleaned up based on the pom.xml settings, and that won't happen for the /tmp directory. > Make Job History File Permissions configurable > -- > > Key: MAPREDUCE-7010 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7010 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Gergely Novák >Priority: Major > Attachments: MAPREDUCE-7010.001.patch, MAPREDUCE-7010.002.patch, > MAPREDUCE-7010.003.patch > > > Currently the mapreduce job history files are written with 770 permissions > which can be accessed by job user or other user part of hadoop group. > There might be users who are not part of the hadoop group but want to access > these history files. We should provide ability to change the default > permissions for staging files. > The default should remain 770. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[
https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376969#comment-16376969
]
Hadoop QA commented on MAPREDUCE-7010:
--
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
14s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
49s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 16m
6s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
42s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
35s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
30s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
11m 30s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
5s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
9s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
9s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
21s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
36s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 32s{color} | {color:orange}
hadoop-mapreduce-project/hadoop-mapreduce-client: The patch generated 6 new +
377 unchanged - 1 fixed = 383 total (was 378) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
10m 35s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
6s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
51s{color} | {color:green} hadoop-mapreduce-client-core in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
52s{color} | {color:green} hadoop-mapreduce-client-common in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 9m
26s{color} | {color:green} hadoop-mapreduce-client-app in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
21s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 68m 25s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:5b98639 |
| JIRA Issue | MAPREDUCE-7010 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12912043/MAPREDUCE-7010.003.patch
|
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit shadedclient findbugs checkstyle xml |
| uname | Linux ebe531cf7721 4.4.0
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376920#comment-16376920 ] Gergely Novák commented on MAPREDUCE-7010: -- Added javadoc and unit test as suggested. > Make Job History File Permissions configurable > -- > > Key: MAPREDUCE-7010 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7010 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Gergely Novák >Priority: Major > Attachments: MAPREDUCE-7010.001.patch, MAPREDUCE-7010.002.patch, > MAPREDUCE-7010.003.patch > > > Currently the mapreduce job history files are written with 770 permissions > which can be accessed by job user or other user part of hadoop group. > There might be users who are not part of the hadoop group but want to access > these history files. We should provide ability to change the default > permissions for staging files. > The default should remain 770. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374553#comment-16374553 ] Billie Rinaldi commented on MAPREDUCE-7010: --- Thanks [~GergelyNovak]. I tried out patch 002 and it appears to work as expected. Could you add a unit test to check return values of getConfiguredHistoryIntermediateUserDoneDirPermissions for various inputs? TestJobHistoryUtils would be one possible place for that. > Make Job History File Permissions configurable > -- > > Key: MAPREDUCE-7010 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7010 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Gergely Novák >Priority: Major > Attachments: MAPREDUCE-7010.001.patch, MAPREDUCE-7010.002.patch > > > Currently the mapreduce job history files are written with 770 permissions > which can be accessed by job user or other user part of hadoop group. > There might be users who are not part of the hadoop group but want to access > these history files. We should provide ability to change the default > permissions for staging files. > The default should remain 770. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[
https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373825#comment-16373825
]
Hadoop QA commented on MAPREDUCE-7010:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
13s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
50s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 16m
1s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
41s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
31s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
23s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
10m 43s{color} | {color:green} branch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
3s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
4s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
9s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
36s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 26s{color} | {color:orange}
hadoop-mapreduce-project/hadoop-mapreduce-client: The patch generated 1 new +
375 unchanged - 1 fixed = 376 total (was 376) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
19s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedclient {color} | {color:green}
10m 1s{color} | {color:green} patch has no errors when building and testing
our client artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
25s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
4s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
50s{color} | {color:green} hadoop-mapreduce-client-core in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
50s{color} | {color:green} hadoop-mapreduce-client-common in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 9m
17s{color} | {color:green} hadoop-mapreduce-client-app in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
25s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 66m 32s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:5b98639 |
| JIRA Issue | MAPREDUCE-7010 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12911228/MAPREDUCE-7010.002.patch
|
| Optional Tests | asflicense comp
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370103#comment-16370103 ] Gergely Novák commented on MAPREDUCE-7010: -- Thanks for the suggestion, [~billie.rinaldi], I implemented your first version (we allow anything starting with 77). If anyone has any reason to prefer the second version, I will update the patch. > Make Job History File Permissions configurable > -- > > Key: MAPREDUCE-7010 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7010 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Gergely Novák >Priority: Major > Attachments: MAPREDUCE-7010.001.patch, MAPREDUCE-7010.002.patch > > > Currently the mapreduce job history files are written with 770 permissions > which can be accessed by job user or other user part of hadoop group. > There might be users who are not part of the hadoop group but want to access > these history files. We should provide ability to change the default > permissions for staging files. > The default should remain 770. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
[jira] [Commented] (MAPREDUCE-7010) Make Job History File Permissions configurable
[ https://issues.apache.org/jira/browse/MAPREDUCE-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369228#comment-16369228 ] Billie Rinaldi commented on MAPREDUCE-7010: --- Thanks for the patch, [~GergelyNovak]! I believe we need to restrict the possible values for the permissions, since user and group both need full permissions on the job history dirs. If group doesn't have write permission, JHS will fail to move the files from intermediate to done dirs and it will trigger MAPREDUCE-7045. I'm not sure if we should allow anything starting with 77, or if we should limit the possible values to 770 or 775. > Make Job History File Permissions configurable > -- > > Key: MAPREDUCE-7010 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-7010 > Project: Hadoop Map/Reduce > Issue Type: Improvement >Reporter: Andras Bokor >Assignee: Gergely Novák >Priority: Major > Attachments: MAPREDUCE-7010.001.patch > > > Currently the mapreduce job history files are written with 770 permissions > which can be accessed by job user or other user part of hadoop group. > There might be users who are not part of the hadoop group but want to access > these history files. We should provide ability to change the default > permissions for staging files. > The default should remain 770. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org
