[
https://issues.apache.org/jira/browse/HBASE-18638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134719#comment-16134719
]
Anoop Sam John commented on HBASE-18638:
----------------------------------------
So this is because of the way we handle the deletes and versions. When the
latest version was deleted, this is not getting counted under the versions. So
the old cell alone is getting exposed to versions and that it count as the 1st
version and given back to client. There is an issue with handling of filtered
out data and versions check. So with deleted data vs versions also same issue?
!
> The old cells will return to client if the new cells are deleted
> ----------------------------------------------------------------
>
> 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: 2.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7
>
> 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
(v6.4.14#64029)
