[ https://issues.apache.org/jira/browse/HBASE-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978214#comment-13978214 ]
Hudson commented on HBASE-10884: -------------------------------- FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #274 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/274/]) HBASE-10884 [REST] Do not disable block caching when scanning (apurtell: rev 1589309) * /hbase/branches/0.98/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/ScannerResultGenerator.java > [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.99.0 > Reporter: Andrew Purtell > Assignee: Andrew Purtell > Fix For: 0.99.0, 0.98.2 > > 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)