Hi Marcell, Since key is changing you will need to rewrite the entire table. I think generating HFlies(rather than doing puts) will be the most efficient here. IIRC, you will need to use HFileOutputFormat in your MR job. For locality, i dont think you should worry that much because major compaction usually takes care of it. If you want very high locality from beginning then you can run a major compaction on new table after your initial load.
HTH, Anil Gupta On Mon, Feb 19, 2018 at 11:46 PM, Marcell Ortutay <mortu...@23andme.com> wrote: > I have a large HBase table (~10 TB) that has an existing key structure. > Based on some recent analysis, the key structure is causing performance > problems for our current query load. I would like to re-write the table > with a new key structure that performs substantially better. > > What is the best way to go about re-writing this table? Since they key > structure will change, it will affect locality, so all the data will have > to move to a new location. If anyone can point to examples of code that > does something like this, that would be very helpful. > > Thanks, > Marcell > -- Thanks & Regards, Anil Gupta
