hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mathias Herberts (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-15487) Deletions done via BulkDeleteEndpoint make past data re-appear
Date Fri, 18 Mar 2016 22:07:33 GMT
Mathias Herberts created HBASE-15487:

             Summary: Deletions done via BulkDeleteEndpoint make past data re-appear
                 Key: HBASE-15487
                 URL: https://issues.apache.org/jira/browse/HBASE-15487
             Project: HBase
          Issue Type: Bug
    Affects Versions: 1.0.3
            Reporter: Mathias Herberts

The Warp10 (www.warp10.io) time series database uses HBase as its underlying data store. The
deletion of ranges of cells is performed using the BulkDeleteEndpoint.

In the following scenario the deletion does not appear to be working properly:

The table 't' is created with a single version using:

REPLICATION_SCOPE => '0', VERSIONS=> '1', MIN_VERSIONS => '0', TTL => '2147483647',
=> 'true'}

We write a cell at row '0x00', colfam 'v', colq '', value 0x0
We write the same cell again with value 0x1

A scan will return a single value 0x1

We then perform a delete using the BulkDeleteEndpoint and a Scan with a DeleteType of 'VERSION'

The reported number of deleted versions is 1 (which is coherent given the table was created

The same scan as the one performed before the delete returns a single value 0x0.

This seems to happen when all operations are performed against the memstore.

A regular delete will remove the cell and a later scan won't show it.

I'll attach a test which demonstrates the problem.

This message was sent by Atlassian JIRA

View raw message