[jira] Commented: (HADOOP-2631) [hbase] 2443 breaks HTable.getStartKeys when there is more than one table or table you are enumerating isn't the first table

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560256#action_12560256 ] 

Hadoop QA commented on HADOOP-2631:
-----------------------------------

+1 overall.  Here are the results of testing the latest attachment 
http://issues.apache.org/jira/secure/attachment/12373432/2631-v2.patch
against trunk revision r613058.

    @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/1634/testReport/
Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1634/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1634/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/1634/console

This message is automatically generated.

> [hbase] 2443 breaks HTable.getStartKeys when there is more than one table or table you are enumerating isn't the first table
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-2631
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2631
>             Project: Hadoop
>          Issue Type: Bug
>          Components: contrib/hbase
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>         Attachments: 2631-v2.patch, 2631.patch
>
>
> Clint Morgan noticed that the current HTable#getStartKeys implementation isn't correct when there are more than one table, or the table you're trying to get the start keys of isn't the only table. I believe that the solution is making sure that the scanner starts at the key that should lead off your table. We should create a TestGetStartKeys test to verify this behavior.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.