You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Mona Chitnis (JIRA)" <ji...@apache.org> on 2012/11/09 21:21:12 UTC
[jira] [Created] (OOZIE-1058) ACL modify-job should not be
hardcoded to group name
Mona Chitnis created OOZIE-1058:
-----------------------------------
Summary: ACL modify-job should not be hardcoded to group name
Key: OOZIE-1058
URL: https://issues.apache.org/jira/browse/OOZIE-1058
Project: Oozie
Issue Type: Bug
Affects Versions: 3.3.0
Reporter: Mona Chitnis
Assignee: Mona Chitnis
Priority: Critical
Fix For: 3.3.0, trunk
OOZIE-907 enables child job ACLs to be applied as default to launcher job. However, the child job's "mapreduce.job.acl-modify-job" is currently hardcoded to user's group name like follows
if (context.getWorkflow().getAcl() != null) {
// setting the group owning the Oozie job to allow anybody in that
// group to kill the jobs.
actionConf.set("mapreduce.job.acl-modify-job", context.getWorkflow().getAcl());
}
As a result, the user provided value for modify-job is disregarded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-1058) ACL modify-job should not be
hardcoded to group name
Posted by "Alejandro Abdelnur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated OOZIE-1058:
--------------------------------------
Fix Version/s: (was: 3.3.0)
3.3.1
> ACL modify-job should not be hardcoded to group name
> ----------------------------------------------------
>
> Key: OOZIE-1058
> URL: https://issues.apache.org/jira/browse/OOZIE-1058
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Priority: Critical
> Fix For: trunk, 3.3.1
>
> Attachments: OOZIE-1058.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> OOZIE-907 enables child job ACLs to be applied as default to launcher job. However, the child job's "mapreduce.job.acl-modify-job" is currently hardcoded to user's group name like follows
> if (context.getWorkflow().getAcl() != null) {
> // setting the group owning the Oozie job to allow anybody in that
> // group to kill the jobs.
> actionConf.set("mapreduce.job.acl-modify-job", context.getWorkflow().getAcl());
> }
> As a result, the user provided value for modify-job is disregarded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-1058) ACL modify-job should not be
hardcoded to group name
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495873#comment-13495873 ]
Hadoop QA commented on OOZIE-1058:
----------------------------------
Testing JIRA OOZIE-1058
Cleaning local svn workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than 132
. {color:green}+1{color} the patch does adds/modifies 1 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
. Tests run: 917
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:green}*+1 Overall result, good!, no -1s*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/173/
> ACL modify-job should not be hardcoded to group name
> ----------------------------------------------------
>
> Key: OOZIE-1058
> URL: https://issues.apache.org/jira/browse/OOZIE-1058
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Priority: Critical
> Fix For: 3.3.0, trunk
>
> Attachments: OOZIE-1058.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> OOZIE-907 enables child job ACLs to be applied as default to launcher job. However, the child job's "mapreduce.job.acl-modify-job" is currently hardcoded to user's group name like follows
> if (context.getWorkflow().getAcl() != null) {
> // setting the group owning the Oozie job to allow anybody in that
> // group to kill the jobs.
> actionConf.set("mapreduce.job.acl-modify-job", context.getWorkflow().getAcl());
> }
> As a result, the user provided value for modify-job is disregarded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OOZIE-1058) ACL modify-job should not be
hardcoded to group name
Posted by "Mona Chitnis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mona Chitnis updated OOZIE-1058:
--------------------------------
Attachment: OOZIE-1058.patch
ReviewBoard
https://reviews.apache.org/r/8028/
> ACL modify-job should not be hardcoded to group name
> ----------------------------------------------------
>
> Key: OOZIE-1058
> URL: https://issues.apache.org/jira/browse/OOZIE-1058
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Priority: Critical
> Fix For: 3.3.0, trunk
>
> Attachments: OOZIE-1058.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> OOZIE-907 enables child job ACLs to be applied as default to launcher job. However, the child job's "mapreduce.job.acl-modify-job" is currently hardcoded to user's group name like follows
> if (context.getWorkflow().getAcl() != null) {
> // setting the group owning the Oozie job to allow anybody in that
> // group to kill the jobs.
> actionConf.set("mapreduce.job.acl-modify-job", context.getWorkflow().getAcl());
> }
> As a result, the user provided value for modify-job is disregarded.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira