Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: <CABd4VQefQQAhwhYH72b6L2QgLq2E3NakkwpS2NbB4hfV=ayX6w@mail.gmail.com>
References: <CABd4VQcU0D47U_Vi9+CsehVdXTCDOoh=rbwvFZP24dQd0ZsxeA@mail.gmail.com>
	<4DC5DDCA-A87C-4A5B-8769-51A482478249@gmail.com>
	<CABd4VQefQQAhwhYH72b6L2QgLq2E3NakkwpS2NbB4hfV=ayX6w@mail.gmail.com>
Date: Sun, 26 Jun 2016 11:00:38 -0400
Message-ID: <CAPQV63VdW9qtfuwYOM9RLKjU7fhjdegES843LwqBvZhmirRqFg@mail.gmail.com>
Subject: Re: Delete row that has columns with future timestamp
From: Jean-Marc Spaggiari <jean-marc@spaggiari.org>
To: user <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c123fe0b3b43805362faa4a
archived-at: Sun, 26 Jun 2016 15:00:46 -0000

--94eb2c123fe0b3b43805362faa4a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

This is a known issue and I think it is solved is more recent versions.  Do
you have the option to upgrade?

JMS
Le 2016-06-26 07:00, "M. BagherEsmaeily" <mbesmaeily@gmail.com> a =C3=A9cri=
t :

> these problem doesn't solve with major compact!! Assuming the problem is
> solved with major compact, in this case, it's still a bug.
>
> On Sun, Jun 26, 2016 at 3:08 PM, Lise Regnier <lise.regnier@gmail.com>
> wrote:
>
> > you need to run a major compact after deletion
> > lise
> >
> > > On 26 Jun 2016, at 11:20, M. BagherEsmaeily <mbesmaeily@gmail.com>
> > wrote:
> > >
> > > Hello
> > > I use HBase version 0.98.9-hadoop1 with Hadoop version 1.2.1 . when i
> > > delete row that has columns with future timestamp, delete not affect
> and
> > > row still surviving.
> > >
> > > For example when i put a row with future timestamp:
> > > Put p =3D new Put(Bytes.toBytes("key1"));
> > > p.add(Bytes.toBytes("C"), Bytes.toBytes("q1"), 2000000000000L,
> > > Bytes.toBytes("test-val"));
> > > table.put(p);
> > >
> > > After put, when i scan my table, the result is:
> > > ROW     COLUMN+CELL
> > > key1    column=3DC:q1, timestamp=3D2000000000000, value=3Dtest-val
> > >
> > > When i delete this row with following code:
> > > Delete d =3D new Delete(Bytes.toBytes("key1"));
> > > table.delete(d);
> > >
> > > OR with this code:
> > > Delete d =3D new Delete(Bytes.toBytes("key1"), Long.MAX_VALUE);
> > > table.delete(d);
> > >
> > > After each two deletes the result of scan is:
> > > ROW     COLUMN+CELL
> > > key1    column=3DC:q1, timestamp=3D2000000000000, value=3Dtest-val
> > >
> > > And raw scan result is:
> > > ROW     COLUMN+CELL
> > > key1    column=3DC:, timestamp=3D1466931500501, type=3DDeleteFamily
> > > key1    column=3DC:q1, timestamp=3D2000000000000, value=3Dtest-val
> > >
> > >
> > > But when i change the timestamp of delete to Long.MAX_VALUE-1, this
> > delete
> > > works. Can anyone help me with this?
> >
> >
>

--94eb2c123fe0b3b43805362faa4a--