>> - *hbase.client.scanner.max.result.size <http://hbase.apache.org/book.html#hbase.client.scanner.max.result.size>*
As documented, the client scanner tries with a max size limit per fetch. See a related: hbase.client.scanner.caching >> - *hbase.server.scanner.max.result.size: **(HBase 13362 <https://issues.apache.org/jira/browse/HBASE-13362>v1.1)* As documented, the server tries to enforce a max size limit per fetch on the server side to protect itself. >> You can retieve rows > 10 Mb Yes, if the row boundary is such. Thanks. Jerry On Sun, Aug 14, 2016 at 3:36 AM, Alberto Ramón <[email protected]> wrote: > Hi, > > We have two properties: > > - *hbase.client.scanner.max.result.size > <http://hbase.apache.org/book.html#hbase.client.scanner.max.result.size > >* > > > - *hbase.server.scanner.max.result.size: **(HBase 13362 > <https://issues.apache.org/jira/browse/HBASE-13362>v1.1)* > > Cloudera blog: > <http://blog.cloudera.com/blog/2015/05/scan-improvements-in-apache-hbase- > 1-1-0/> > "The max result size limit is only applied at row boundaries. " > > I don't understand because, if you put client max.result.size = 10 MB > > You can retieve rows > 10 Mb > > > BR, Alberto >
