[
https://issues.apache.org/jira/browse/HBASE-11635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14083172#comment-14083172
]
Nick Dimiduk commented on HBASE-11635:
--------------------------------------
The config is only used by TableMapReduceUtil.setScannerCaching; not used at
all by the version based on the scanner, right? We should get rid of the config
at the same time we get ride of TableMapReduceUtil.setScannerCaching so that
only the serialized Scan object is used.
Since we have master branch at 2.0.0-SNAPSHOT, you can provide the patches for
0.98 and branch-1 that deprecate the method and warn on config access, and a
patch for master that removes "hbase.client.scanner.caching" and
TableMapReduceUtil.setScannerCaching -- both on this ticket. No need to open
separate JIRA for deprecation and removal. If you choose to do that, update the
title accordingly.
> 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)
