Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 83006 invoked from network); 16 Jan 2008 00:32:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Jan 2008 00:32:04 -0000 Received: (qmail 3489 invoked by uid 500); 16 Jan 2008 00:31:52 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 3460 invoked by uid 500); 16 Jan 2008 00:31:52 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 3451 invoked by uid 99); 16 Jan 2008 00:31:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jan 2008 16:31:52 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2008 00:31:48 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 28BB4714247 for ; Tue, 15 Jan 2008 16:31:40 -0800 (PST) Message-ID: <18642957.1200443500163.JavaMail.jira@brutus> Date: Tue, 15 Jan 2008 16:31:40 -0800 (PST) From: "Hairong Kuang (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Updated: (HADOOP-2543) No-permission-checking mode for smooth transition to 0.16's permissions features. In-Reply-To: <7300548.1199755894075.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-2543: ---------------------------------- Attachment: permissionRelated.patch The patch added a "secret" configuration parameter "dfs.upgrade.permission" with a default value of 0777. If an administrator wants to use a different value for the initial permission, he/she can set it in hadoop-site.xml. > No-permission-checking mode for smooth transition to 0.16's permissions features. > ---------------------------------------------------------------------------------- > > Key: HADOOP-2543 > URL: https://issues.apache.org/jira/browse/HADOOP-2543 > Project: Hadoop > Issue Type: New Feature > Components: dfs > Affects Versions: 0.15.1 > Reporter: Sanjay Radia > Assignee: Hairong Kuang > Fix For: 0.16.0 > > Attachments: permissionRelated.patch > > > In moving to 0.16, which will support permissions, a mode of no-permission checking has been proposed to allow smooth transition to using the new permissions feature. > The idea is that at first 0.16 will be used for a period of time with permission checking off. > Later after the admin has changed ownership and permissions of various files, the permission checking can be turned off. > This Jira defines what the semantics are of the no-permission-checking mode. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.