[ https://issues.apache.org/jira/browse/HBASE-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208757#comment-13208757 ]
Amitanand Aiyer commented on HBASE-5241: ---------------------------------------- @Lars. Sure. I see there can be issues with replication. Is that something that cannot be fixed? I am not really familiar with the replication code path. But, say, if we ship the memstoreTS along with the KV's during replication; would that not take care of the out of order issue? > 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 > Attachments: HBASE-5241.D1731.1.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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira