By cloning snapshot you will have same number of regions in source and destination table. If you want more pre-split in destination table then you will have to use CopyTable tool. Simply create new table with same column families as destination table and pre-split it with number of regions you want then run CopyTable tool.
Regards Samir On Wed, Jan 20, 2016 at 12:24 PM, Ted Yu <[email protected]> wrote: > There is also backup / restore (work in progress): > > https://issues.apache.org/jira/browse/HBASE-7912 > > FYI > > On Wed, Jan 20, 2016 at 2:12 AM, Samir Ahmic <[email protected]> > wrote: > > > Hi Sumit, > > IMHO snapshots are easiest way to copy tables you need just to steps: > > > > 1. create snapshot > > 2. clone snapshot to another table > > > > What version of hbase you are using? Regarding you question what will > > happen in case operation fails in case of cloning snapshot i have never > > experience such event if snapshot was not corrupted. In case of CopyTable > > mr i assume that data will be partially copied. In any case your source > > tables will be OK. > > > > > > Regards > > Samir > > > > On Wed, Jan 20, 2016 at 7:51 AM, Sumit Nigam > <[email protected] > > > > > wrote: > > > > > Hi, > > > I have a a few tables in hbase which I would like to create copies of. > > The > > > tables will be in same cluster. > > > I wanted to know based on experience, which one of the options is > better: > > > 1. copyTable2. snapshot3. Any other? > > > Besides efficiency aspect, I am also interested in knowing what happens > > > when the operation fails midway copying from snapshot to destination > > table. > > > Or when it fails midway copying to destination table in copyTable > option. > > > Would data be left in inconsistent state? > > > Thanks,Sumit > > >
