[
https://issues.apache.org/jira/browse/HBASE-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545447#comment-14545447
]
Jingcheng Du commented on HBASE-13531:
--------------------------------------
bq. We will read cells from MOB files only on demand right. First we read from
ref cf files and there any way the readPoint check is there. Only if it passes,
we will call get cell on MOB.
Or the case is like with same key (rk,cf,q,ts,type) we have 2 cells and old
cell in ref cf got cleared by readPoint check but we read the new cell from MOB
file?
Hi Anoop [~anoopsamjohn], I think we could directly use the readPt to directly
seek the cell in mob file. I have refined the patch based on the V1, and will
upload it later.
> 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
>
> Attachments: HBASE-13531-V2.diff, HBASE-13531-V3.diff,
> HBASE-13531.diff
>
>
> 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)
