Return-Path: Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: (qmail 53980 invoked from network); 20 Aug 2010 15:42:20 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Aug 2010 15:42:20 -0000 Received: (qmail 45888 invoked by uid 500); 20 Aug 2010 15:42:20 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 45808 invoked by uid 500); 20 Aug 2010 15:42:19 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 45800 invoked by uid 99); 20 Aug 2010 15:42:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Aug 2010 15:42:19 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com designates 209.85.216.41 as permitted sender) Received: from [209.85.216.41] (HELO mail-qw0-f41.google.com) (209.85.216.41) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Aug 2010 15:42:14 +0000 Received: by qwk4 with SMTP id 4so3377745qwk.14 for ; Fri, 20 Aug 2010 08:41:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=LonyKKcKdJ5aAwQrzqUFXHn3YuiszNJFRAOpFFuktdc=; b=w634FmeoiMU+LG1XqREp5qWcFJDeXSXLX2WYiJbhPkcb/9l5Dte4tm9TYagu9HfpDZ Lx6bzJ5ttyTEo8NMcI5fDyuHq6sXOCCI3EwnL0eCDDyPGkC8RmSRw9Vo5OUs0OFufKQS fypTJSIgx58oPvTB2Dj3rDLOjE93GlwU3RZbE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=H9nQ+RWKv4f9QnwoiX4ZeXGtq3ii7RhS0AhnVH6rti2xB1qO1N46Vqcl37cpCNeqId 4W6H6HSxGWOclQIhXDqRfMw18aj7yCz21chiRZy8IMObjfvDF9KmmvgOP863Qls9cZA6 H5Xn6idRkswyBJOa65If3Xd7MSXoDG029x3+w= MIME-Version: 1.0 Received: by 10.224.37.19 with SMTP id v19mr1100411qad.66.1282318913429; Fri, 20 Aug 2010 08:41:53 -0700 (PDT) Received: by 10.229.48.129 with HTTP; Fri, 20 Aug 2010 08:41:53 -0700 (PDT) In-Reply-To: References: Date: Fri, 20 Aug 2010 08:41:53 -0700 Message-ID: Subject: Re: How row delete works From: Ted Yu To: dev@hbase.apache.org Content-Type: multipart/alternative; boundary=001517503cc852e2ee048e43235c --001517503cc852e2ee048e43235c Content-Type: text/plain; charset=ISO-8859-1 Please refer to this method in HRegion.java: public void delete(Map> familyMap, boolean writeToWAL) Also read the javadoc at the beginning of Delete.java On Fri, Aug 20, 2010 at 2:51 AM, Gagandeep Singh wrote: > Hi > > Can somebody please shed some light on the internal working of the HBase > delete operation. So when I perform a delete operation what exactly happens > underneath the code. Is my data removed immediately from the disk or else a > flag is set by HBase to mark those rows as deleted. > > Thanks, > Gagan > --001517503cc852e2ee048e43235c--