[
https://issues.apache.org/jira/browse/HADOOP-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559283#action_12559283
]
Hadoop QA commented on HADOOP-2592:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12373152/tti.patch
against trunk revision r612258.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1602/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1602/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1602/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1602/console
This message is automatically generated.
> [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
> Assignee: stack
> Priority: Critical
> Fix For: 0.16.0
>
> 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.
