[
https://issues.apache.org/jira/browse/HBASE-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17121317#comment-17121317
]
Andrew Olson commented on HBASE-13541:
--------------------------------------
I realize it's been over 5 years since this issue was opened, but I'm curious
what the current status of it is?
> Deprecate Scan caching in 2.0.0
> -------------------------------
>
> Key: HBASE-13541
> URL: https://issues.apache.org/jira/browse/HBASE-13541
> Project: HBase
> Issue Type: Sub-task
> Reporter: Jonathan Lawlor
> Priority: Major
> Attachments: HBASE-13541-WIP.patch
>
>
> The public Scan API exposes caching to the application. Caching deals with
> the number of rows that are transferred per scan RPC request issued to the
> server. It does not seem like a detail that users of a scan should control
> and introduces some unneeded complication. Seems more like a detail that
> should be controlled from the server based on the current scan request RPC
> load. This issue proposes that we deprecate the caching API in 2.0.0 so that
> it can be removed later. Of course, if there are any concerns please raise
> them here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
