Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <27429000.358191285208973397.JavaMail.jira@thor>
Date: Wed, 22 Sep 2010 22:29:33 -0400 (EDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1415) Group name is not properly set in
 inodes
In-Reply-To: <24963870.357881285205853832.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913884#action_12913884 ] 

dhruba borthakur commented on HDFS-1415:
----------------------------------------

Code looks good to me. I wonder why the HDFS namenode was not using the group information in the first place, it seemed like a pretty reasonable thing to do. Maybe Owen has some historical perspective on this?

Do we need to put some javadocs to state that if there are multiple groups in the ugi, then the first one takes efffect as far as file permissions are concerned?

Also, this looks like an incompatible change, especially because files will now have the appropriate group information.

> Group name is not properly set in inodes
> ----------------------------------------
>
>                 Key: HDFS-1415
>                 URL: https://issues.apache.org/jira/browse/HDFS-1415
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Scott Chen
>            Assignee: Scott Chen
>         Attachments: HDFS-1415.txt
>
>
> In NameNode.create() and NameNode.mkdirs() do not pass the group name. So it is not properly set.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.