July 18, 2012 8:33 PM
To: user@hbase.apache.org
Subject: Re: Table not storing versions after deleteall
Zoltan,
It's actually a bit more complicated because the behavior is
non-deterministic. If a compaction happens the delete marker may be
removed, and if you add the rows back after t
Sent: Wednesday, July 18, 2012 7:26 PM
> To: user@hbase.apache.org
> Subject: Re: Table not storing versions after deleteall
>
> The deleteall marker will hide everything that comes before its
> timestamp (in your case it's current time), if you just want to delete
> specific values use de
On Wed, Jul 18, 2012 at 10:32 AM, Zoltán Tóth-Czifra
wrote:
> Thanks for the quick answer! So I understand it's the expected behavior...?
Yeah, it's an edge case.
> For me it doesn't explain why can't I re-add the exact same rows.
As I mentioned, they are hidden by the delete marker. Basically,
pache.org]
Sent: Wednesday, July 18, 2012 7:26 PM
To: user@hbase.apache.org
Subject: Re: Table not storing versions after deleteall
The deleteall marker will hide everything that comes before its
timestamp (in your case it's current time), if you just want to delete
specific values use delete inste
The deleteall marker will hide everything that comes before its
timestamp (in your case it's current time), if you just want to delete
specific values use delete instead.
Hope this helps,
J-D
On Wed, Jul 18, 2012 at 10:19 AM, Zoltán Tóth-Czifra
wrote:
> Hi,
>
> For a few days now I'm fighting w
Hi,
For a few days now I'm fighting with a very strange behaviour of Hbase. I hope
you can explain it to me.
In short: add rows with version, delete all rows, add the same rows again, old
rows disappear.
I create a table, add some rows, some of them with explicit timestamp. After
this, I can r
