[jira] [Comment Edited] (HBASE-10884) [REST] Do not disable block caching when scanning

["Andrew Purtell (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965513#comment-13965513 ] 

Andrew Purtell edited comment on HBASE-10884 at 4/10/14 6:01 PM:
-----------------------------------------------------------------

Test failure is not related, will commit soon.

Ping [~stack] and [~lhofhansl], this is a trivial patch and perf improvement, but limited to REST use cases. However it is a behavioral change without recourse without HBASE-10952, and that introduces a new query parameter and field to the Scanner model in a backwards compatible way.


was (Author: apurtell):
Test failure is not related, will commit soon.

Ping [~stack] and [~lhofhansl], I'm going to assume no objection to trivial patch and perf improvement, but limited to REST use cases.

> [REST] Do not disable block caching when scanning
> -------------------------------------------------
>
>                 Key: HBASE-10884
>                 URL: https://issues.apache.org/jira/browse/HBASE-10884
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.98.1, 0.96.1.1, 0.94.18
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>         Attachments: HBASE-10884.patch
>
>
> The REST gateway pessimistically disables block caching when issuing Scans to the cluster, using Scan#setCacheBlocks(false) in ScannerResultGenerator. It does not do this when issuing Gets on behalf of HTTP clients in RowResultGenerator. This is an old idea now, the reasons for doing so lost sometime back in the era when HBase walked the earth with dinosaurs (< 0.20). We probably should not be penalizing REST scans in this way. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)