You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/02 18:43:32 UTC
[jira] [Resolved] (MAPREDUCE-1665) kill and modify should not be
the same acl
[ https://issues.apache.org/jira/browse/MAPREDUCE-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved MAPREDUCE-1665.
-----------------------------------------
Resolution: Won't Fix
We don't believe in granular control.
> kill and modify should not be the same acl
> ------------------------------------------
>
> Key: MAPREDUCE-1665
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1665
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: security
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Allen Wittenauer
>
> The permission to kill a job/task should be split out from modification. There are definitely instances where someone who can kill a job should not be able to modify it. [Third person job monitoring, for example, such as we have here at LinkedIn.]
--
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