No problem! I'll add it to the book because this applies to the CopyTable utility as well, and you're not the first to ask this question.
On 1/12/12 12:36 PM, "Jahangir Mohammed" <[email protected]> wrote: >Thanks Doug, missed it. > >Thanks, >Jahangir. > >On Thu, Jan 12, 2012 at 10:34 AM, Doug Meil ><[email protected]>wrote: > >> >> setCaching is set in TableInputFormat, and it relies on the following >> property set in the jobconf... >> >> job.getConfiguration().setInt("hbase.client.scanner.caching", >> batchSize); >> >> >> >> >> >> >> On 1/11/12 11:13 PM, "Jahangir Mohammed" <[email protected]> >>wrote: >> >> >Hello, >> > >> >Have couple of questions around hbase "export" facility: >> >1. I was looking at Export code. >> > >> >>http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/mapreduce/Export. >>h >> >tml. >> >I don't see "setCaching" called in the code. Wouldn't that would have >> >speed >> >up the hbase export. Is this intentional? or is it expected that user >> >change this conf in hbase-site.xml according to their memory >>constraints. >> >Am I missing anything here? >> > >> >2. While running hbase export for backing up data, I am getting scanner >> >timeout exceptions too. I can increase the regionserver.lease.period >>but >> >not sure whether it's a good idea. >> > >> >Would be nice to hear some opinions. Any help greatly appreciated. >> > >> >Thanks, >> >Jahangir. >> >> >>
