Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BFD74D9CE for ; Mon, 12 Nov 2012 19:35:12 +0000 (UTC) Received: (qmail 56913 invoked by uid 500); 12 Nov 2012 19:35:12 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 56767 invoked by uid 500); 12 Nov 2012 19:35:12 -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 56758 invoked by uid 99); 12 Nov 2012 19:35:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2012 19:35:12 +0000 Date: Mon, 12 Nov 2012 19:35:12 +0000 (UTC) From: "Aaron T. Myers (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <28981967.102216.1352748912397.JavaMail.jiratomcat@arcas> In-Reply-To: <1452627230.66213.1352056333020.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (HDFS-4148) disallow modification on RO snapshots 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-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495539#comment-13495539 ] Aaron T. Myers commented on HDFS-4148: -------------------------------------- How about a hybrid solution along the following lines: * Keep SnapshotException as it is used today, i.e. only for snaphot-related operations. * Introduce a new SnapshotAccessControlException which extends AccessControlException. * Have this patch throw the new SnapshotAccessControlException wherever a user tries to modify a RO snapshot. This way programs which currently handle AccessControlException won't have to be changed, but programs that do want to differentiate on this basis will be able to catch a specific exception. This also has the advantage of not conflating client access errors with snapshot operations exceptions, which I think are semantically different types of errors. > disallow modification on RO snapshots > -------------------------------------- > > Key: HDFS-4148 > URL: https://issues.apache.org/jira/browse/HDFS-4148 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: name-node > Affects Versions: Snapshot (HDFS-2802) > Reporter: Brandon Li > Assignee: Brandon Li > Attachments: HDFS-4148.patch, HDFS-4148.patch > > > disallow modification on RO snapshots, including create, append, setReplication/Permission/Owner, rename, delete, makedir, setQuota/Time, createSymlink. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira