You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Virag Kothari (JIRA)" <ji...@apache.org> on 2012/07/12 19:58:35 UTC

[jira] [Commented] (OOZIE-907) Default ACL settings for Oozie launcher

    [ https://issues.apache.org/jira/browse/OOZIE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413005#comment-13413005 ] 

Virag Kothari commented on OOZIE-907:
-------------------------------------

*The patch overrides the 'oozie.launcher' settings with the default setting. This seems to be opposite of what is stated in JIRA.
*Only if the property exists, it should be set. Otherwise it will be set to null which is undesirable
if (actionConf.exists(CONF_OOZIE_ACL_VIEW_JOB)){
  launcherConf.set()
}
*TestCases need to account for the cases in above comments
*Other launcher related conf is done within JavaActionExecutor. What is the need for creating a static method in LauncherMapper?



                
> 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
>
>   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