hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-4439) Move ClientScanner out of HTable
Date Tue, 20 Sep 2011 21:24:09 GMT

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

Lars Hofhansl updated HBASE-4439:

    Attachment: 4439.txt

1st cut. Very simple change, mostly just moves some code around.

* simply moves HTable.ClientScanner to its own toplevel class. ClientScanner is now useable
without an instance of an HTable.
* HTable.getScanner(scan) now clones the scan. Even previously the scan object was actually
modified inside the ClientScanner.
* Some config options (maxScannerResultSize, scannerTimeout)
* deprecates HTable.{get|set}ScannerCaching, so that scannerCaching can also be removed from
HTable. Caching should be set through the scan object or the cluster wide config option instead.

> Move ClientScanner out of HTable
> --------------------------------
>                 Key: HBASE-4439
>                 URL: https://issues.apache.org/jira/browse/HBASE-4439
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.94.0
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>            Priority: Minor
>             Fix For: 0.94.0
>         Attachments: 4439.txt
> See HBASE-1935 for motivation.
> ClientScanner should be able to exist outside of HTable.
> While we're at it, we can also add an abstract client scanner to easy development of
new client side scanners (such as parallel scanners, or per region scanners).

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message