Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of kylelin2000@gmail.com
 designates 209.85.220.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5A9A57920BD5514FA7E38922FBC875D9257B2BF4@EX-MBOX1.xiaomi.net>
References: 
 <CAP4=KSPC2joQzHwQfqRC8LtGh9j9ADsCGaHjRHm_sT=shW2KMg@mail.gmail.com>
	<5A9A57920BD5514FA7E38922FBC875D9257B2BF4@EX-MBOX1.xiaomi.net>
Date: Thu, 13 Jun 2013 10:41:26 +0800
Message-ID: 
 <CAP4=KSPZwqM01nefjC8oNk4Jp6k0gry=BhCPK_UU0d4MxLqSqQ@mail.gmail.com>
Subject: 
 =?Big5?Q?Re=3A_=B5=AA=CE=60=3A_Scanning_not_show_the_correct_value_of_l?=
	=?Big5?Q?atest_version?=
From: Kyle Lin <kylelin2000@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff1bfb41a04c804df0011e9

--e89a8ff1bfb41a04c804df0011e9
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Hello Hong Hua

   I've do some experiments and really got the rule of deletion. Thanks for
your explanation.

2013/6/12 =B7=EB=BA=EA=BB=AA <fenghonghua@xiaomi.com>

> hi, Kyle
>
> This is NOT a bug. There are three types of delete: Delete, DeleteColumn,
> DeleteFamily; Delete is actually DeleteCell which can only mask(delete) a
> cell with exactly the SAME timestamp, in your below case, "* Row1
>                      column=3Dcf:c2, timestamp=3D1370935373545, type=3DDe=
lete" is
> a Delete (DeleteCell) so it can only mask(delete) " Row1   column=3Dcf:c2=
,
> timestamp=3D1370935373545, value=3Dkk" since they have the same timestamp=
s, but
> can't mask(delete) "Row1  column=3Dcf:c2, timestamp=3D1370935357741, valu=
e=3Dh
> *" since they have different timestamps
>
> DeleteColumn can do what you expect: it can mask(delete) cells under the
> column with timestamps less or equal to the timestamp of the DeleteColumn
>
> --Honghua
>
> ________________________________________
> =B7=A2=BC=FE=C8=CB: Kyle Lin [kylelin2000@gmail.com]
> =B7=A2=CB=CD=CA=B1=BC=E4: 2013=C4=EA6=D4=C211=C8=D5 16:58
> =CA=D5=BC=FE=C8=CB: user@hbase.apache.org
> =D6=F7=CC=E2: Scanning not show the correct value of latest version
>
> Hey Guys
>
>     After I modifying a cell many times with delete action, The result of
> scan is not correct.
>
>     I Expect the value of "Row1 cf:c2" is null because I've delete the
> cell(The line with blue color below). But I actually got "h"(The line wit=
h
> green color below).
>
>     Is this a hbase bug? Or my operating fault?
>
> hbase(main):007:0> scan 'table42', {RAW =3D> true, VERSIONS =3D> 3}
> ROW
> COLUMN+CELL
>
>  Row1                                column=3Dcf:c1, timestamp=3D13709353=
57679,
> value=3De
> * Row1                                column=3Dcf:c2,
> timestamp=3D1370935373545, type=3DDelete
>
>  Row1                                column=3Dcf:c2, timestamp=3D13709353=
73545,
> value=3Dkk
>  Row1                                column=3Dcf:c2, timestamp=3D13709353=
57741,
> value=3Dh   *
>  Row2                                column=3Dcf:c1, timestamp=3D13709353=
57804,
> value=3Dp
>  Row2                                column=3Dcf:c2, timestamp=3D13709353=
80939,
> value=3Dpp
>  Row2                                column=3Dcf:c2, timestamp=3D13709353=
73582,
> value=3Djj
>  Row2                                column=3Dcf:c2, timestamp=3D13709353=
57774,
> value=3Dd
> 2 row(s) in 0.0220 seconds
>
> hbase(main):008:0> scan 'table42'
> ROW
> COLUMN+CELL
>
>  Row1                                column=3Dcf:c1, timestamp=3D13709353=
57679,
> value=3De
> * Row1                                column=3Dcf:c2,
> timestamp=3D1370935357741, value=3Dh  *
>
>  Row2                                column=3Dcf:c1, timestamp=3D13709353=
57804,
> value=3Dp
>  Row2                                column=3Dcf:c2, timestamp=3D13709353=
80939,
> value=3Dpp
> 2 row(s) in 0.0200 seconds
>
>
> *P.S. My HBase Version is 0.94.6*
>
>
> Kyle
>

--e89a8ff1bfb41a04c804df0011e9--