bq.  imported htable has only one region left

This table had one region before the import, right ?

You can obtain the region boundaries from the original table and split the
target table accordingly.

Cheers

On Thu, Feb 5, 2015 at 11:10 PM, hongbin ma <[email protected]> wrote:

> hi,
>
> For test purpose, we're trying to export a test hbase table and import it
> into a minicluster using org.apache.hadoop.hbase.mapreduce.Export
> and org.apache.hadoop.hbase.mapreduce.Import.
> The thing is, there was four regions in our original htable, but after
> Importing, the imported htable has only one region left. (The exported
> files are organized into four files, however)
> We need to keep the region count as it was, is there any configurations for
> this? Or do I have any other options?
>
> cheers
> hongbin
>

Reply via email to