[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493833
]
Kurtis Heimerl commented on HADOOP-1298:
----------------------------------------
I'll go through those in order.
I think the first is a valid point. I think the problem is in the existing API
though. I don't need the array of file listings either though, and grabbing the
0th one seems like a hack. I also think opening the file seems to heavy-weight.
Second-> Why? We could move rename, delete, exists and a bunch of other methods
under one header as well, but it just confuses the code. Since these will need
to be multiplexed at a lower level, why not keep the code path clean and
obvious?
3-> again, why? If we're going to do that, we can move most of the methods like
that.
4-> will do
5-> good point. I'll look at that too.
> 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
> Attachments: hadoop-user-munncha.patch, hadoop-user-munncha.patch,
> hadoop-user-munncha.patch, hadoop-user-munncha.patch4,
> hadoop-user-munncha.patch5, hadoop-user-munncha.patch6,
> hadoop-user-munncha.patch7, hadoop-user-munncha.patch8,
> hadoop-user-munncha.patch9
>
>
> 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.
