You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/01/29 21:08:34 UTC
[jira] Resolved: (HADOOP-2631) [hbase] 2443 breaks
HTable.getStartKeys when there is more than one table or table you are
enumerating isn't the first table
[ https://issues.apache.org/jira/browse/HADOOP-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HADOOP-2631.
---------------------------
Resolution: Fixed
Fix Version/s: 0.16.0
Committed (Thanks Bryan and Dennis Kubes for noticing this hadn't actually been committed).
> [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 Core
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: Bryan Duxbury
> Assignee: stack
> Priority: Blocker
> Fix For: 0.16.0
>
> 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.