hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1873) User permissions for Map/Reduce
Date Wed, 28 Nov 2007 20:00:55 GMT

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

Allen Wittenauer commented on HADOOP-1873:
------------------------------------------

(I totally admit that I'm only half paying attention this and I feel guilt about that... but...
)

> Will we permit per-file permissions? Wasn't there some discussion that we should only
support per-directory permissions?

If you don't do per-file permissions, directories like /tmp become a major battle ground as,
at least in our experiences, everybody expects to be able to write there... so then the question
becomes, how do you protect users from overwriting each other in what are essentially public
directories?

[Although, this does beg another question: should hadoop have the equiv. of mkstemp() and
friends?]

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


Mime
View raw message