[
https://issues.apache.org/jira/browse/HADOOP-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-2592:
--------------------------
Attachment: tti.patch
Should fix the failures we've been seeing today in TestTableIndex
M src/contrib/hbase/src/java/org/apache/hadoop/hbase/HStoreFile.java
Renamed topFirstNextCall as firstNextCall
(HalfMapFile.getClosest): If serving the bottom half, though we check the key
we're looking for is < midkey, nothing to stop the call
to the super.getClosest returning a key in excess of midkey. Add a check.
> [hbase] Scanning, a region can let out a row that its not supposed to have
> --------------------------------------------------------------------------
>
> Key: HADOOP-2592
> URL: https://issues.apache.org/jira/browse/HADOOP-2592
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: stack
> Priority: Minor
> Attachments: test3.patch, tti.patch
>
>
> Bryan's lazy cache patch was provoking a strange issue in TestTableIndex when
> flush size was small -- 64k instead of 1MB -- where a scan was returning
> random rows twice, w/ the second incidence coming out of a region whose range
> shouldn't even contain the row.
> After study, HalfMapFiles serving the top half of a parent region down in the
> daughter, can have rows in excess of the region endkey; scanning, the call to
> next will just return these rows w/ consideration of whether beyond region
> endkey.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
