[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526185
]
Doug Cutting commented on HADOOP-1298:
--------------------------------------
> Do we have a plan for how a user's ID gets assigned to files his reduce job
> creates, or how his map job's read "his" files?
Only a rough one at this point. The idea is that the client submits an
authorization ticket along with each job, then the tasktracker uses that ticket
when accessing the filesystem. Folks who are serious will use something like
Kerberos, which is well suited. By default, the ticket will just be a
username, with no authentication.
There are still a number of open issues, like whether the ticket should be
stored as a job configuration property or as a separate parameter to job
submission. We should probably start a separate issue for mapred's filesystem
authorization.
> adding user info to file
> ------------------------
>
> Key: HADOOP-1298
> URL: https://issues.apache.org/jira/browse/HADOOP-1298
> Project: Hadoop
> Issue Type: New Feature
> Components: dfs, fs
> Reporter: Kurtis Heimerl
> Assignee: Christophe Taton
> Fix For: 0.15.0
>
> Attachments: 1298_2007-09-06b.patch, 1298_2007-09-07g.patch,
> hadoop-user-munncha.patch17
>
>
> I'm working on adding a permissions model to hadoop's DFS. The first step is
> this change, which associates user info with files. Following this I'll
> assoicate permissions info, then block methods based on that user info, then
> authorization of the user info.
> So, right now i've implemented adding user info to files. I'm looking for
> feedback before I clean this up and make it offical.
> I wasn't sure what release, i'm working off trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
