We had a bunch of discussion about changing that default, but then decided to leave it in 0.94 to follow the "principle of the least surprise". See also https://issues.apache.org/jira/browse/HBASE-7008
-- Lars ________________________________ From: Patrick Schless <[email protected]> To: user <[email protected]> Sent: Thursday, July 11, 2013 9:37 AM Subject: Re: hbase.client.scanner.caching - default 1, not 100 Cool, thanks, I didn't realize I could get a 0.94 version of that doc. Very useful :) On Thu, Jul 11, 2013 at 11:32 AM, Ted Yu <[email protected]> wrote: > For 0.94, the following should be referenced: > http://hbase.apache.org/0.94/book.html > > I searched for hbase.client.scanner.caching > In section 2.3.1, you would see that its value is 1. > > Cheers > > On Thu, Jul 11, 2013 at 9:28 AM, Patrick Schless > <[email protected]>wrote: > > > In 0.94 I noticed (in the "Job File") my job VerifyRep job was running > with > > hbase.client.scanner.caching set to 1, even though the hbase docs [1] say > > it defaults to 100. I didn't have that property being set in any of my > > configs. I added the properties to hbase-site.xml (set to 100), and now > > that job runs with 100, as expected. Is it possible that that docs are > > wrong? > > > > [1] http://hbase.apache.org/book/config.files.html > > >
