You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/04/22 07:58:00 UTC
[jira] [Updated] (HBASE-28540) Cache Results in org.apache.hadoop.hbase.rest.client.RemoteHTable.Scanner
[ https://issues.apache.org/jira/browse/HBASE-28540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HBASE-28540:
-----------------------------------
Labels: pull-request-available (was: )
> Cache Results in org.apache.hadoop.hbase.rest.client.RemoteHTable.Scanner
> -------------------------------------------------------------------------
>
> Key: HBASE-28540
> URL: https://issues.apache.org/jira/browse/HBASE-28540
> Project: HBase
> Issue Type: Improvement
> Components: REST
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Minor
> Labels: pull-request-available
>
> The implementation of org.apache.hadoop.hbase.rest.client.RemoteHTable.Scanner
> is very inefficient, as the standard next() methods makes separate a http request for each row.
> Performance can be improved by not specifying the row count in the REST call and caching the returned Results.
> Chunk size can still be influenced by scan.setBatch();
--
This message was sent by Atlassian Jira
(v8.20.10#820010)