Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 18 Sep 2012 04:39:09 +1100 (NCT)
From: "Karthik Ranganathan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <869623197.88632.1347903549155.JavaMail.jiratomcat@arcas>
In-Reply-To: <761574742.72682.1347498247870.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6770) Allow scanner setCaching to specify
 size instead of number of rows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Karthik Ranganathan commented on HBASE-6770:
--------------------------------------------

Agreed. If that's the only issue, then passing a hint makes it easier to use - do something like setPartialRowScanning(true) if we want to respect that. But in any case, I am not suggesting removing the existing API, just adding the new ones.
                
> Allow scanner setCaching to specify size instead of number of rows
> ------------------------------------------------------------------
>
>                 Key: HBASE-6770
>                 URL: https://issues.apache.org/jira/browse/HBASE-6770
>             Project: HBase
>          Issue Type: Bug
>          Components: client, regionserver
>            Reporter: Karthik Ranganathan
>
> Currently, we have the following api's to customize the behavior of scans:
> setCaching() - how many rows to cache on client to speed up scans
> setBatch() - max columns per row to return per row to prevent a very large response.
> Ideally, we should be able to specify a memory buffer size because:
> 1. that would take care of both of these use cases.
> 2. it does not need any knowledge of the size of the rows or cells, as the final thing we are worried about is the available memory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira