hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-514) table 'does not exist' when it does
Date Thu, 29 May 2008 16:59:45 GMT

    [ https://issues.apache.org/jira/browse/HBASE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600838#action_12600838

stack commented on HBASE-514:

Would suggest you update to 0.1.2.  Lots of critical fixes including fixes for what you are
seeing above, I'd guess.  No migration needed going between 0.1.1 and 0.1.2 so upgrade is
just matter of replacing the software.

Regards your schema, why have so many families?  Would suggest you put the content into one
family and then all other attributes into another family.

Good to hear you have a writer for Heritrix (Is it based off the work by Ankur Goel -- and
the code I passed him)?

FYI, rather than stick your question into a closed issue, you might do better next time posting
to the list.

> table 'does not exist' when it does
> -----------------------------------
>                 Key: HBASE-514
>                 URL: https://issues.apache.org/jira/browse/HBASE-514
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.16.0
>            Reporter: stack
>            Assignee: Bryan Duxbury
>             Fix For: 0.1.0
>         Attachments: 514-0.1-v2.patch, 514-0.1-v3.patch, 514-0.1.patch, region-v2.patch
> This one I've seen a few times.  In hql, I do show tables and it shows my table.  I then
try to do a select against the table and hql reports table does not exist.  Digging, whats
happening is that the getClosest facility is failing to find the first table region in the
.META. table.  I hacked up a region reading tool -- attached (for 0.1 branch) -- and tried
it against but a copy and the actual instance of the region and it could do the getClosest
fine.  I'm pretty sure I restarted the HRS and when it came up again, the master had given
it again the .META. and again was failing to find the first region in the table (Looked around
in server logs and it seemed 'healthy').

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

View raw message