hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: Hbase shell - deletall doesnt remove records
Date Thu, 20 Feb 2014 21:28:14 GMT
The familyStamp kept by ScanDeleteTracker is of the time when deleteall was
This value is lower than the large long value given in your example.
Meaning the following check wouldn't pass:

    if (hasFamilyStamp && timestamp <= familyStamp) {

leading to isDeleted() returning DeleteResult.NOT_DELETED. Thus the get
would still return the row.

Can you tell us more about your use case where the large long value is used


On Thu, Feb 20, 2014 at 1:19 AM, Ron Sher <ronsher@gmail.com> wrote:

> I work with Yaniv and we now have a better understanding of the issue.
> It happens when you specifically set a timestamp that is a large long
> value.
> For example 635265926417915010
> If you then try to delete the whole line, without specifying the timestamp,
> thinking that it will delete the whole line it simply doesn't work. You get
> no errors, but when you later try to get that line - you get it back.
> There is a constant repro:
> Lets say we have a table called t1 with some CF content
> put 't1', 'blah', 'content:document', '{}', 635265926417915010
> get 't1', 'blah'
> deleteall 't1', 'blah'
> get 't1', 'blah'
> --
> View this message in context:
> http://apache-hbase.679495.n3.nabble.com/Hbase-shell-deletall-doesnt-remove-records-tp4056162p4056189.html
> Sent from the HBase User mailing list archive at Nabble.com.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message