[
https://issues.apache.org/jira/browse/HBASE-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096965#comment-13096965
]
stack commented on HBASE-4311:
------------------------------
I agree we should create hbck clean tables.
FYI, the gymnastics being done in createMultiRegion precedes the createTable
that took a list of regions. In other words, I don't think we need do it this
way any more. Could just do
http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/HBaseAdmin.html#createTable(org.apache.hadoop.hbase.HTableDescriptor,
byte[][]) I believe.
(You might not be able to do the above w/ the createTableWithLegacy calls
though)
> HBaseTestingUtility.createMultiRegions generates table that fails in hbck.
> --------------------------------------------------------------------------
>
> Key: HBASE-4311
> URL: https://issues.apache.org/jira/browse/HBASE-4311
> Project: HBase
> Issue Type: Bug
> Reporter: Jonathan Hsieh
> Assignee: Jonathan Hsieh
>
> When refactoring TestHBaseFsckRepair to add more hbck test cases, I noticed
> that HBaseTestingUtility.createMultiRegions uses an existing table with empty
> region, adds more regions, and then attempts to remove the region. The
> region remains in meta and is causes hbck to report at inconsistency. Ideally
> these test table generation utility functions should generate clean tables.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
