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 B4DF59B1C for ; Mon, 26 Mar 2012 21:14:51 +0000 (UTC) Received: (qmail 20155 invoked by uid 500); 26 Mar 2012 21:14:51 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 20097 invoked by uid 500); 26 Mar 2012 21:14:51 -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 20087 invoked by uid 99); 26 Mar 2012 21:14:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2012 21:14:51 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2012 21:14:48 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id A49DE34709F for ; Mon, 26 Mar 2012 21:14:27 +0000 (UTC) Date: Mon, 26 Mar 2012 21:14:27 +0000 (UTC) From: "Scott Carey (Commented) (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <877568285.19602.1332796467677.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1897228862.19412.1332794790721.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-3154) Add a notion of immutable/mutable files 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-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238841#comment-13238841 ] Scott Carey commented on HDFS-3154: ----------------------------------- You should be able to make a copy of an immutable file that takes up no extra space, but can be appended to or truncated. The immutable file and the copy would share immutable blocks. > Add a notion of immutable/mutable files > --------------------------------------- > > Key: HDFS-3154 > URL: https://issues.apache.org/jira/browse/HDFS-3154 > Project: Hadoop HDFS > Issue Type: New Feature > Components: name-node > Reporter: Tsz Wo (Nicholas), SZE > Assignee: Tsz Wo (Nicholas), SZE > > The notion of immutable file is useful since it lets the system and tools optimize certain things as discussed in [this email thread|http://mail-archives.apache.org/mod_mbox/hadoop-hdfs-dev/201203.mbox/%3CCAPn_vTuZomPmBTypP8_1xTr49Sj0fy7Mjhik4DbcAA+BLH53=g@mail.gmail.com%3E]. Also, many applications require only immutable files. Here is a proposal: > - Immutable files means that the file content is immutable. Operations such as append and truncate that change the file content are not allowed to act on immutable files. However, the meta data such as replication and permission of an immutable file can be updated. Immutable files can also be deleted or renamed. > - Users have to pass immutable/mutable as a flag in file creation. This is an unmodifiable property of the created file. > - If users want to change the data in an immutable file, the file could be copied to another file which is created as mutable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira