hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-13734) Improper timestamp checking with VisibilityScanDeleteTracker
Date Thu, 21 May 2015 04:48:59 GMT

     [ https://issues.apache.org/jira/browse/HBASE-13734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anoop Sam John updated HBASE-13734:
-----------------------------------
    Attachment: HBASE-13734.patch

> Improper timestamp checking with VisibilityScanDeleteTracker
> ------------------------------------------------------------
>
>                 Key: HBASE-13734
>                 URL: https://issues.apache.org/jira/browse/HBASE-13734
>             Project: HBase
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 0.98.4
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0, 0.98.13, 1.0.2, 1.2.0, 1.1.1
>
>         Attachments: HBASE-13734.patch
>
>
> 3 issues
> 1. When VC is used and all the put cells and delete cells are not having any visibility
associated with them, we are not correctly checking put cells ts against that of delete cell
resulting in deletion of cells coming in after the delete ts
> 2. Have a row r1 with 2 cells of same TS but different visibility. In order to delete
both cells we have to apply 2 deletes with these 2 visibility being set to Delete. We are
trying to do this using delete full row option or delete cf way. But only one cell is getting
deleted.
> 3. Same case as in #2 when I try to delete using family version delete, only one cell
is getting deleted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message