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] [Commented] (HBASE-15487) Deletions done via BulkDeleteEndpoint make past data re-appear
Date Mon, 21 Mar 2016 13:21:25 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204165#comment-15204165
] 

Mathias Herberts commented on HBASE-15487:
------------------------------------------

You are right, the initial feeling was that it was related to the BulkDeleteEP but after more
experiments it appears it is an issue with HBase behavior.

I did not file the issue to have my BDEP problem solved, as I mentioned in the comments I've
done that already. I filed the issue to try to assess if this is a bug in HBase or an expected
behavior which should be more throughly documented.

My sentiment at this point is that the Put0 / Put1 / Delete sequence with versions == 1 should
not return the result of 'Put0', so let's focus on this point rather than on the initial BDEP
problem which was only indirectly related.

> 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
>         Attachments: HBaseTest.java, HBaseTest.java
>
>
> 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:
> create 't', {NAME => 'v', DATA_BLOCK_ENCODING => 'FAST_DIFF', BLOOMFILTER =>
'NONE', REPLICATION_SCOPE => '0', VERSIONS=> '1', MIN_VERSIONS => '0', TTL =>
'2147483647', KEEP_DELETED_CELLS => 'false', BLOCKSIZE => '65536', IN_MEMORY =>'false',
BLOCKCACHE => '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
with MAX_VERSIONS=1)
> 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
(v6.3.4#6332)

Mime
View raw message