[
https://issues.apache.org/jira/browse/HBASE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601021#action_12601021
]
Pratyush Banerjee commented on HBASE-514:
-----------------------------------------
Dear Stack,
Sorry about the inconvenience caused. Actually putting the log data in the mail
made my office server detect it as a spam and hence i was unable to send a mail
to the group.?
Thanks for your suggestions. I will definitely upgrade to 0.1.2. Your
suggestions regrading the schema is also very helpful, we would look into it to
make necessary adjustments.
Yes this is indeed the code that was worked upon by Ankur Goel, he happens to
be my teammate !!!
thanks and regards
Pratyush
> 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.
