[
https://issues.apache.org/jira/browse/OOZIE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mona Chitnis updated OOZIE-907:
-------------------------------
Attachment: OOZIE-907v3.patch
After discussing with Mohammad, removing the prefix "oozie.launcher" of the ACL
properies from the launcherConf object since it is stripped for the other
properties as well.
Also, changed the function into reusable code applicable to other set of
properties too.
Addressed Virag's comment and separated out the tests case-by-case for clarity
> 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, OOZIE-907v3.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
