[
https://issues.apache.org/jira/browse/HBASE-8770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001964#comment-14001964
]
stack commented on HBASE-8770:
------------------------------
Fixing this makes sense to me. Especially after unification of MVCC and seqid
and if seqid lives on into hfiles -- if not per key, at least keep around a
seqid on the file. As is, the behavior 'surprises'. HBASE-9905 is something
else.
Fix seems 'simple' enough, changing the order at which we evaluate Cell/KV
elements in the comparator; we'd swap (or remove type consideration) with
sequence id in the order in which we run the compare.
> deletes and puts with the same ts should be resolved according to mvcc/seqNum
> -----------------------------------------------------------------------------
>
> Key: HBASE-8770
> URL: https://issues.apache.org/jira/browse/HBASE-8770
> Project: HBase
> Issue Type: Brainstorming
> Reporter: Sergey Shelukhin
> Priority: Critical
>
> This came up during HBASE-8721. Puts with the same ts are resolved by seqNum.
> It's not clear why deletes with the same ts as a put should always mask the
> put, rather than also being resolve by seqNum.
> What do you think?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
