Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 92665 invoked from network); 27 Apr 2010 21:17:00 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Apr 2010 21:17:00 -0000 Received: (qmail 92070 invoked by uid 500); 27 Apr 2010 21:17:00 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 92038 invoked by uid 500); 27 Apr 2010 21:17:00 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 92030 invoked by uid 99); 27 Apr 2010 21:17:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Apr 2010 21:17:00 +0000 X-ASF-Spam-Status: No, hits=-1356.7 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Apr 2010 21:16:59 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o3RLGcFH022030 for ; Tue, 27 Apr 2010 21:16:39 GMT Message-ID: <16014800.42011272402998844.JavaMail.jira@thor> Date: Tue, 27 Apr 2010 17:16:38 -0400 (EDT) From: "Milind Bhandarkar (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Commented: (HDFS-1113) Allow users with write access to a directory to change ownership of its subdirectories/files In-Reply-To: <4142786.41691272402513650.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12861547#action_12861547 ] Milind Bhandarkar commented on HDFS-1113: ----------------------------------------- >From what I have heard in brief conversations with File system experts, the requirement to be a superuser to chown or chgroup in Posix came about because of the need to stop abuse of user-level quotas. I could abuse the quotas, by changing ownership of my files/directories to someone else, so that these files/directories are counted against their quota, not mine. In HDFS, we have directory-based quotas, and not user-based. So, this scenario does not hold true. (Is there any other reason for allowing chown only by superuser in Posix?) If we allow chown, chgrp, setQuota and clrQuota operations on subdirectories for the owner of the directory, then it will ease operations of shared large clusters. HDFS administrators will have to simply create directories such as: /data/BusinessUnit1, /data/BusinessUnit2.., set the BU-specific quotas, set ownership to the respective BU leaders. Afterward, creating subdirectories under these directories for users/projects/teams, managing their quotas etc is the responsibility of the BU leader, and not of the central HDFS administrators. Thoughts ? > Allow users with write access to a directory to change ownership of its subdirectories/files > -------------------------------------------------------------------------------------------- > > Key: HDFS-1113 > URL: https://issues.apache.org/jira/browse/HDFS-1113 > Project: Hadoop HDFS > Issue Type: New Feature > Components: name-node > Environment: All > Reporter: Milind Bhandarkar > Assignee: Sanjay Radia > > owner and group of a file/directory, and namespace/diskspace quota for a directory are mutable attributes. If I have writable access to a directory, say /team/MyTeam, and if there are subdirectories underneath, such as /team/MyTeam/TeamMember1, /team/MyTeam/TeamMember2, then I should be able to chown, chgrp, setQuota, clrQuota on TeamMemeber{1|2} subdirectories. Currently in HDFS (and in Posix), it requires me to be a superuser to perform these operations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.