You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by hongbin ma <ma...@apache.org> on 2015/02/06 08:10:02 UTC

Hbase table export and import

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

Re: Hbase table export and import

Posted by hongbin ma <ma...@apache.org>.
Got it , so I'll have to properly configure the "empty" table before
importing.
I was expecting Import program to intelligently handle it.

thanks
hongbin

On Fri, Feb 6, 2015 at 10:53 PM, Ted Yu <yu...@gmail.com> wrote:

> 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 <ma...@apache.org> 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
> >
>

Re: Hbase table export and import

Posted by Ted Yu <yu...@gmail.com>.
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 <ma...@apache.org> 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
>