[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528673
]
Sameer Paranjpye commented on HADOOP-1298:
------------------------------------------
> Indeed, but that substantially changes semantics.
It does significantly affect how we use a connection. But single user is the
common use case. My concern is that this change will be required as we try to
scale the Namenode to more and more clients. Rather than break the protocol now
and then again, would it make sense to invest in ticket caching now?
Jobtracker --> Namenode interactions on behalf of a user could be handled by
having a 'change user' operation on a connection. This would have some overhead
but less than the overhead of passing and decrypting a ticket per RPC.
> 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.
