Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 45969 invoked from network); 17 Dec 2009 12:23:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Dec 2009 12:23:29 -0000 Received: (qmail 80795 invoked by uid 500); 17 Dec 2009 12:23:25 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 80663 invoked by uid 500); 17 Dec 2009 12:23:25 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 80643 invoked by uid 99); 17 Dec 2009 12:23:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2009 12:23:25 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of starrysl@gmail.com designates 209.85.223.193 as permitted sender) Received: from [209.85.223.193] (HELO mail-iw0-f193.google.com) (209.85.223.193) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2009 12:23:23 +0000 Received: by iwn31 with SMTP id 31so1444679iwn.5 for ; Thu, 17 Dec 2009 04:23:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:content-type; bh=MdG0vRnveyUEKK2KKQaufuLM03+SIkzSURN1qrRLohs=; b=w3e+6dKR/FZTp8CEugSh/VznuULct/vmacZ5JYenoZwCX42PR8kFt4xNZPigoLhG6j J5pFs3ZWLq0TORyywSuz+hqQUFV5/lnRpOtaWbsuxfMBhTPjt//m2+QrGguUSKFtLEW1 kirEO52ZSfMu6za3HlDwQBMla8cu6TXaM+oBU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=fTWa5OQ3PrUzpyM6tsWG8J6MyQqe9E/jv0NpYRmmzjy4iYapVGiTsiQgUttdM23pne WtpBRhXrY2VsUJDvrVzLKKVwFY4Dqh+uUJy6VEddnOYETuHRH/LFQpmAkhN+e9KJOpdp wKGrIY5kl9smwg2duzm/ajSjuDZLq8gmD42Zg= MIME-Version: 1.0 Received: by 10.231.157.83 with SMTP id a19mr378082ibx.41.1261052582190; Thu, 17 Dec 2009 04:23:02 -0800 (PST) From: Starry SHI Date: Thu, 17 Dec 2009 20:22:42 +0800 Message-ID: Subject: permission control in HDFS To: common-user@hadoop.apache.org, common-dev@hadoop.apache.org Content-Type: multipart/alternative; boundary=0050450169f3346034047aebaf07 --0050450169f3346034047aebaf07 Content-Type: text/plain; charset=UTF-8 Hi. I wonder how permission control can be used in HDFS? I am using hadoop 0.20.1, and I have 3 user accessing to HDFS. I use user1's account to create a file and chmod 600 to this file in HDFS. However, I tried to use user2 and user3's account to access the file belonging to user1, they can still read the contents of the file!!! This means the permission control is no use in HDFS. What I tried to do is to avoid user2 and user3 to read the file from user1 stored in HDFS. In the configuration I have already set dfs.permissions as "true". Can somebody tell me how to enable permission control in HDFS? Best regards, Starry /* Tomorrow is another day. So is today. */ --0050450169f3346034047aebaf07--