Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of erikholstad@gmail.com
 designates 209.85.216.185 as permitted sender)
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=Ifzm2i7qPlwpzUOJRzlmjSh/F9dBGtnzjUpbBy4m9i4TtX1bviw/zi1OreDufRL9SK
         +9Bfr3vO4FJnXuBf+HAT6fuLuqtWBDO4wN3aYr1cQKZwh0n2pHsN4XwhGx1CM1K64Fi8
         YVf7gFJmhtl+aV39gW+Ze8vV2whjJ+mIw10nQ=
MIME-Version: 1.0
In-Reply-To: <4B951C3E.4030107@kalooga.com>
References: <4B94F35E.4090506@kalooga.com>
	 <74f4d40b1003080709g70abf838qf06a7492e70ffd22@mail.gmail.com>
	 <4B951C3E.4030107@kalooga.com>
Date: Mon, 8 Mar 2010 07:58:06 -0800
Message-ID: <74f4d40b1003080758q7429ec8at911a5704ffea4106@mail.gmail.com>
Subject: Re: Best way to do a clean update of a row
From: Erik Holstad <erikholstad@gmail.com>
To: hbase-user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=0016e64dc8fe7fc7a804814c212f

--0016e64dc8fe7fc7a804814c212f
Content-Type: text/plain; charset=ISO-8859-1

Hey Ferdy!
Not really sure what you are asking now. But if you do a deleteRow and then
a put in the same
milli second the put will be "shadowed" by the delete so that it will not
show up when you look
for later, if that makes sense? The reason for this is that deletes are
sorted before puts for the
same timestamp, so for a put to be viewable it needs to have a newer
timestamp than the delete.


-- 
Regards Erik

--0016e64dc8fe7fc7a804814c212f--