Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <4187809.271691266210208818.JavaMail.jira@brutus.apache.org>
Date: Mon, 15 Feb 2010 05:03:28 +0000 (UTC)
From: "Vinod K V (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Updated: (MAPREDUCE-1307) Introduce the concept of Job
 Permissions
In-Reply-To: <1188257451.1261029258069.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod K V updated MAPREDUCE-1307:
---------------------------------

    Attachment: MAPREDUCE-1307-20100215.txt

Updated patch fixing tests and adding mapreduce.cluster.job-authorization-enabled.

> Introduce the concept of Job Permissions
> ----------------------------------------
>
>                 Key: MAPREDUCE-1307
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1307
>             Project: Hadoop Map/Reduce
>          Issue Type: Sub-task
>          Components: security
>            Reporter: Devaraj Das
>            Assignee: Vinod K V
>             Fix For: 0.22.0
>
>         Attachments: 1307-early-1.patch, MAPREDUCE-1307-20100210.txt, MAPREDUCE-1307-20100211.txt, MAPREDUCE-1307-20100215.txt
>
>
> It would be good to define the notion of job permissions analogous to file permissions. Then the JobTracker can restrict who can "read" (e.g. look at the job page) or "modify" (e.g. kill) jobs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.