Dave Latham commented on HBASE-8770:

Is the performance penalty for this behavior due to having deleted versions 
count against max versions?  Or just for this change?


It really seems like this should become the default behavior for hbase at some 
major release, hopefully without any significant performance penalty, 
independent of the question of whether deleted versions count against max 

> 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
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 2.0.0
>         Attachments: HBASE-8770.branch-2.001.patch, 
> HBASE-8770.branch-2.002.patch
> 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

Reply via email to