[
https://issues.apache.org/jira/browse/HBASE-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084206#comment-14084206
]
Ishan Chhabra commented on HBASE-11635:
---------------------------------------
[~ndimiduk], The config is also used by hbase client to decide the value of
caching if it is not set on the scan object. Here is the relevant piece of code
from ClientScanner.java
{code}
// Use the caching from the Scan. If not set, use the default cache
setting for this table.
if (this.scan.getCaching() > 0) {
this.caching = this.scan.getCaching();
} else {
this.caching = conf.getInt(
HConstants.HBASE_CLIENT_SCANNER_CACHING,
HConstants.DEFAULT_HBASE_CLIENT_SCANNER_CACHING);
}
{code}
If we deprecate and remove the config, it also means that you cannot set
caching at the client side using this config. Is that ok?
> Deprecate TableMapReduceUtil.setScannerCaching
> ----------------------------------------------
>
> Key: HBASE-11635
> URL: https://issues.apache.org/jira/browse/HBASE-11635
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Affects Versions: 1.0.0, 0.98.4, 2.0.0
> Reporter: Ishan Chhabra
> Assignee: Ishan Chhabra
>
> See discussion in HBASE-11558.
> Currently there are 2 ways to specify scanner caching when invoking a MR job
> using TableMapReduceUtil.
> 1. By setting the caching on the Scan Object.
> 2. By setting the "hbase.client.scanner.caching" config using
> TableMapReduceUtil.setScannerCaching.
> This JIRA attempts to deprecate the latter.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
