You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2007/12/19 21:43:43 UTC

[jira] Issue Comment Edited: (HADOOP-1873) User permissions for Map/Reduce

    [ https://issues.apache.org/jira/browse/HADOOP-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553482 ] 

hairong edited comment on HADOOP-1873 at 12/19/07 12:43 PM:
------------------------------------------------------------------

This patch makes the following changes to map/reduce:
1. JobTracker removes all the files/subdirectories under the map/reduce system instead of removing the mapreduce system directory. If the system directory does not exist, it creates it with the permission \-wx\-wx\-wx. This requires that the runner of the job tracker is the same as the namenode.
2. JobClient creates job direoctories using the permission \-wx\-wx\-wx and creates job files using the permission rw\-r\-\-r\-\-. It also stores its user id in the job configuration.

      was (Author: hairong):
    This patch makes the following changes to map/reduce:
1. JobTracker removes all the files/subdirectories under the map/reduce system instead of removing the mapreduce system directory. If the system directory does not exist, it creates it with the right permission -wx-wx-wx. This requires that the runner of the job tracker is the same as the namenode.
2. JobClient creates job direoctories using the permission -wx-wx-wx and creates job files using the permission rw-r--r--. It also stores its user id in the job configuration.
  
> User permissions for Map/Reduce
> -------------------------------
>
>                 Key: HADOOP-1873
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1873
>             Project: Hadoop
>          Issue Type: Improvement
>            Reporter: Raghu Angadi
>            Assignee: Hairong Kuang
>         Attachments: mapred.patch
>
>
> HADOOP-1298 and HADOOP-1701 add permissions and pluggable security for DFS files and DFS accesses. Same users permission should work for Map/Reduce jobs as well. 
> User persmission should propegate from client to map/reduce tasks and all the file operations should be subject to user permissions. This is transparent to the user (i.e. no changes to user code should be required). 

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