[
https://issues.apache.org/jira/browse/OOZIE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414197#comment-13414197
]
Mona Chitnis commented on OOZIE-907:
------------------------------------
If user has specified value for the property 'mapreduce.job.acl-view-job' or
modify-job, then that will get set. otherwise it will get set to the group
name. I can add a notNull condition for this launcherJobConf property in the
block
if (context.getWorkflow().getAcl() != null) {
// setting the group owning the Oozie job to allow anybody in
that
// group to kill the jobs.
launcherJobConf.set("mapreduce.job.acl-modify-job",
context.getWorkflow().getAcl());
}
> Default ACL settings for Oozie launcher
> ---------------------------------------
>
> Key: OOZIE-907
> URL: https://issues.apache.org/jira/browse/OOZIE-907
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk, 3.2.1
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: trunk, 3.2.1
>
> Attachments: OOZIE-907.patch, OOZIE-907v2.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> This is about the oozie settings:
> - oozie.launcher.mapreduce.job.acl-view-job
> - oozie.launcher.mapreduce.job.acl-modify-job
> Currently, these settings default to the most restrictive permissions.
> Instead they should default to the values set by the user
> for the settings:
> - mapreduce.job.acl-view-job => oozie.launcher.mapreduce.job.acl-view-job
> - mapreduce.job.acl-modify-job =>
> oozie.launcher.mapreduce.job.acl-modify-job
> Typically, users will want to set these same values for the mapreduce and
> oozie settings, so its a reasonable default.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
