hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christophe Taton (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (HADOOP-1779) Small INodeDirectory enhancement to get all existing INodes components on a path
Date Thu, 30 Aug 2007 03:40:30 GMT

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

kryzthov edited comment on HADOOP-1779 at 8/29/07 8:38 PM:
-------------------------------------------------------------------

Indeed, I did not take this into account.
Do you already have a scheme in mind for distributing the namenode so that I can think about
it?
Is this going to be implemented soon?

Permission checking can be implemented in many ways. The implementation I have in mind allows
you to easily switch to different authorization models. It only requires you to rewrite the
Policy provider (see HADOOP-1298)...
In the current implementation I want to push, authorizations follow regular POSIX file permissions
(except there is no group right for now). This model and its implementation is sufficient
in most basic cases to my mind, and for a quite short-term perspective, unless namenode distributed
is planned for, say, before the end of the year? And again, if this basic permission checking
mechanism conflicts with namenode distribution, we will be able to switch either its implementation
or its model...

What do you think?

      was (Author: kryzthov):
    Indeed, I did not take this into account.
Do you already have a scheme in mind for distributing the namenode so that I can think about
it?
Is this going to be implemented soon?

  
> Small INodeDirectory enhancement to get all existing INodes components on a path
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-1779
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1779
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Christophe Taton
>            Assignee: Christophe Taton
>            Priority: Trivial
>             Fix For: 0.15.0
>
>         Attachments: 1779_2007-08-27c.patch
>
>
> This patch introduces {{INode[] INodeDirectory.getExistingPathINodes(String path)}},
modeled over the existing {{getNode()}} / {{getINode()}}.
> The purpose of this is to provide a way to retrieve all existing INodes in a path in
a single tree scan.
> This to allow fast INode's permission (see [HADOOP-1298|https://issues.apache.org/jira/browse/HADOOP-1298])
checking along the path, and without requiring the {{INode.parent}} field which could be removed
(see [HADOOP-1687|https://issues.apache.org/jira/browse/HADOOP-1687]).

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