[jira] [Updated] (OOZIE-1058) ACL modify-job should not be hardcoded to group name

["Virag Kothari (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OOZIE-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Virag Kothari updated OOZIE-1058:
---------------------------------

    Fix Version/s:     (was: 3.3.1)
                       (was: trunk)
                   3.3.0
    
> 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
>
>         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