[
https://issues.apache.org/jira/browse/HBASE-8770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038097#comment-16038097
]
Phil Yang commented on HBASE-8770:
----------------------------------
bq. If not, would simply changing the sort order to order by seq id before cell
type for this issue be a possibility for 2.0?
We will remove mvcc in HFile in minor compaction (to save capacity) and
delete/put will have same mvcc if they are in one same file. If I am not wrong
we can not just change the comparator :( At least we should always keep mvcc in
HFiles just like HBASE-15968 does.
bq. Is there hope for HBASE-15968 to make it into 2.0?
The patch is available and I think we can get it in after rebasing and
reviewing. But we need more tests (I am testing in our own cluster) and I am
not sure if it can be a default behavior because the performance will be a
little worse and a new feature may have some bugs... So I prefer to always keep
mvcc in HFile by default, compare mvcc before type by default, but the other
behavior is configurable.
> 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.3.15#6346)
