You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ashok shetty (Jira)" <ji...@apache.org> on 2019/09/12 11:56:00 UTC

[jira] [Commented] (HBASE-18638) There are version-related dirty data caused by delete/ttl

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

Ashok shetty commented on HBASE-18638:
--------------------------------------

I was going through this Jiar and  reproduced the issue in my cluster as mentioned above . I even tried with creating multiple Hfiles and triggered Major Compaction on table but result is same But , 
when i  performed flush operation before detele operation and then get row result is No_Records.

steps followed 
1.create 'test','cf'
2.put 'test','r1','cf','100'
3.put 'test','r1','cf','200'
4.flush 'test'
5.delete 'test','r1','cf'
6.get 'test','r1'

result 0 rows 

> There are version-related dirty data caused by delete/ttl
> ---------------------------------------------------------
>
>                 Key: HBASE-18638
>                 URL: https://issues.apache.org/jira/browse/HBASE-18638
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.3.1, 1.2.6, 2.0.0-alpha-1
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Critical
>             Fix For: 3.0.0, 1.5.0
>
>         Attachments: HBASE-18638-ut.patch, HBASE-18638-ut.patch
>
>
> |put_0(t0)|
> |put_1(t1)|  <-- the latest cell
> If we call get, the put_1 will return. That is good.
> If we call get after a delete, the put_0 will return. That is weird. The put_0 is old data, and it should be dropped in flush. For client, put_0 should not exist after the put_1 happen.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)