As refguide states, hbase.client.scanner.caching works
with hbase.client.scanner.max.result.size to try and use the network
efficiently.
Make sure the release you use is 1.1.0+ which had important bug fixes
w.r.t. max result size.
On Wed, Jan 11, 2017 at 9:46 AM, Josh Elser wrote:
> Behind the
Behind the scenes, the ClientScanner is buffering results from the
previous RPC. Ignoring multiple RegionServers for now, the caching value
denotes the number of records that were fetched by the ClientScanner in
an RPC. When the buffered results are consumed by your client, a new RPC
will be ma
I have hbase.client.scanner.caching as 100. I am scanning a table. For
instance say we have 500 rows matching for the current scan. When I give
the statement ResultScanner.next() what will happen? whether it will return
100 rows for each next operation or something else
Thanks
