Pre-splitting was discussed a few times on the mailing list today, and a few times in the past weeks, for example: http://search-hadoop.com/m/XB9Vr1gQc66
Import works on a pre-existing table so it won't recreate it. Also it doesn't know how your key space is constructed, so it cannot guess the start/stop row keys for you. J-D On Tue, Mar 29, 2011 at 2:33 PM, Venkatesh <[email protected]> wrote: > Thanks J-D > > We have way too much data & it won't fit in 1 region.Is Import smart enough > create > reqd # of regions? > > Cld u pl. elaborate on pre-split table creation? steps? > > Reason I'm doing this exercise is reduce # of regions in our cluster (in the > absence of additional hardware >> 25K regions on 20 node) > > > > > > > > > > > -----Original Message----- > From: Jean-Daniel Cryans <[email protected]> > To: [email protected] > Sent: Tue, Mar 29, 2011 5:29 pm > Subject: Re: Export/Import and # of regions > > > Yes but you'll start with a single region, instead of truncating you > > probably want instead to create a pre-split table. > > > > J-D > > > > On Tue, Mar 29, 2011 at 2:27 PM, Venkatesh <[email protected]> wrote: > >> > >> > >> > >> Hi, > >> If I export existing table using Export MR job, truncate the table, increase > > region size, & do a Import > >> will it make use of the new region size? > >> > >> thanks > >> V > >> > >> > >> > > > >
