[
https://issues.apache.org/jira/browse/HBASE-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449540#comment-13449540
]
Jonathan Hsieh commented on HBASE-5631:
---------------------------------------
I haven't encountered this situation but for a first cut we should do the bare
minimum to get a functional table again. I agree that at a bare minimum we can
infer the table name and the colfam names from the dir structure. Once those
are up, a user could alter the table to "fix" the other parameters. A second
cut (follow on jira issue) could probably look at the newest hfile in each
colfam and get some of the parameters (compression settings, encodings, etc).
> hbck should handle case where .tableinfo file is missing.
> ---------------------------------------------------------
>
> Key: HBASE-5631
> URL: https://issues.apache.org/jira/browse/HBASE-5631
> Project: HBase
> Issue Type: Improvement
> Components: hbck
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Reporter: Jonathan Hsieh
> Assignee: Jie Huang
> Attachments: hbase-5631.patch
>
>
> 0.92+ branches have a .tableinfo file which could be missing from hdfs. hbck
> should be able to detect and repair this properly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
