[
https://issues.apache.org/jira/browse/HBASE-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526233#comment-14526233
]
ramkrishna.s.vasudevan commented on HBASE-13531:
------------------------------------------------
bq.Cells with the same row/cf/cq/ts should have a last written wins policy
I think while retrieving we don't have this guarentee. When the same
row/cf/cq/ts is written in the same file I think only the older one is
retrieved because our scan here is going to be sequential. And while flushing
we don't check for duplicates I believe. We just write what is in memstore.
> After 4/18/15 merge, flakey failures of
> TestAcidGuarantees#testMobScanAtomicity
> -------------------------------------------------------------------------------
>
> Key: HBASE-13531
> URL: https://issues.apache.org/jira/browse/HBASE-13531
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver, Scanners
> Affects Versions: hbase-11339
> Reporter: Jonathan Hsieh
> Fix For: hbase-11339
>
>
> After the merge of master from 4/18/15 with hbase-11339 branch, we encounter
> some atomicity violations. We want to fix before calling merge to trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
