Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 22 Mar 2012 22:02:22 +0000 (UTC)
From: "Milind Bhandarkar (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1878001591.5002.1332453742329.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2049515590.23016.1331873625982.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-3107) HDFS truncate
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236086#comment-13236086 ] 

Milind Bhandarkar commented on HDFS-3107:
-----------------------------------------

bq. We don't need unowned block. The block should be owned by the user since the data of the block is.

Sorry, by "unowned", I meant block that does not belong to any file. If a separate block management becomes an external first class citizen, one could have existing blocks added to a new namespace (from what I remember in the vision discussions with Sanjay last year), and concat could take a list of blocks instead of a file.

Lei, do you see any issues with the proposal (i.e option 2) ?
                
> HDFS truncate
> -------------
>
>                 Key: HDFS-3107
>                 URL: https://issues.apache.org/jira/browse/HDFS-3107
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: data-node, name-node
>            Reporter: Lei Chang
>         Attachments: HDFS_truncate_semantics_Mar15.pdf, HDFS_truncate_semantics_Mar21.pdf
>
>   Original Estimate: 1,344h
>  Remaining Estimate: 1,344h
>
> Systems with transaction support often need to undo changes made to the underlying storage when a transaction is aborted. Currently HDFS does not support truncate (a standard Posix operation) which is a reverse operation of append, which makes upper layer applications use ugly workarounds (such as keeping track of the discarded byte range per file in a separate metadata store, and periodically running a vacuum process to rewrite compacted files) to overcome this limitation of HDFS.

--
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