-Re: hbase.client.scanner.caching - default 1, not 100
lars hofhansl 2013-07-11, 21:00
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
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
On Thu, Jul 11, 2013 at 11:32 AM, Ted Yu <[EMAIL PROTECTED]> wrote:
> For 0.94, the following should be referenced:
> I searched for hbase.client.scanner.caching
> In section 2.3.1, you would see that its value is 1.
> 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
> > hbase.client.scanner.caching set to 1, even though the hbase docs  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?
> >  http://hbase.apache.org/book/config.files.html