You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2011/09/20 23:26:09 UTC
[jira] [Commented] (HBASE-4439) Move ClientScanner out of HTable
[ https://issues.apache.org/jira/browse/HBASE-4439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109005#comment-13109005 ]
Lars Hofhansl commented on HBASE-4439:
--------------------------------------
Hit submit too early...
* Some config options (maxScannerResultSize, scannerTimeout) are moved from HTable to ClientScanner.
* ClientScanner uses static logger.
Could consider abstracting useful parts in a helper class if we foresee that writing new client scanners would be a common client side task.
> 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