hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Xiang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-6770) Allow scanner setCaching to specify size instead of number of rows
Date Thu, 25 Apr 2013 18:06:15 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jimmy Xiang resolved HBASE-6770.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.89-fb
    
> 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: Sub-task
>          Components: Client, regionserver
>            Reporter: Karthik Ranganathan
>            Assignee: Chen Jin
>             Fix For: 0.89-fb
>
>
> 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

Mime
View raw message