[OOZIE-1058] ACL modify-job should not be hardcoded to group name

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Fix Version/s: 3.3.0
• Assignee: Mona Chitnis
• Reporter: Mona Chitnis
• Created: 09/Nov/12 20:21
• Updated: 26/Jan/13 00:54
• Resolved: 03/Dec/12 18:37

Description

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.