You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/12 20:06:00 UTC

[jira] [Resolved] (HBASE-5241) Deletes should not mask Puts that come after it.

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

Andrew Kyle Purtell resolved HBASE-5241.
----------------------------------------
      Assignee:     (was: Amitanand Aiyer)
    Resolution: Abandoned

> Deletes should not mask Puts that come after it.
> ------------------------------------------------
>
>                 Key: HBASE-5241
>                 URL: https://issues.apache.org/jira/browse/HBASE-5241
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Amitanand Aiyer
>            Priority: Major
>         Attachments: ASF.LICENSE.NOT.GRANTED--HBASE-5241.D1731.1.patch, ASF.LICENSE.NOT.GRANTED--HBASE-5241.D1731.2.patch, ASF.LICENSE.NOT.GRANTED--HBASE-5241.D1731.3.patch
>
>
> Suppose that we have a delete row, and then followed by the put. The delete row
> can mask the put, unless there was a major compaction in between.
> Now that we are flushing the memstoreTS to disk, along with the KVs, we should be able
> to differentiate whether or not the Put happened after the Delete and offer better 
> delete semantics.
> Couldn't find a pre-existing JIRA that already discusses this, so creating one.
> Seems related to https://issues.apache.org/jira/browse/HBASE-2406, but is not quite the same.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)