You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2016/11/20 06:53:59 UTC

[jira] [Commented] (HBASE-16984) Implement getScanner

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

Duo Zhang commented on HBASE-16984:
-----------------------------------

[~carp84] [~stack] In this patch I have introduced two types of AsyncTable. One is RawAsyncTable and the other is AsyncTable. The old AsyncTableImpl is now called RawAsyncTableImpl.

The difference between these two interfaces is that, you need to provide a thread pool when creating AsyncTable so it is safe to do everything in the callbak method as it will be executed in the thread pool and will not block the rpc framework. So it is more suitable for normal user. The RawAsyncTable is used to build high performance service.

The old scan method is only introduced in RawAsyncTable and getScanner is only introduced in AsyncTable.

Will open another jira to commit the interface changes first if you guys think it is OK.

Thanks.

> Implement getScanner
> --------------------
>
>                 Key: HBASE-16984
>                 URL: https://issues.apache.org/jira/browse/HBASE-16984
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>    Affects Versions: 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16984.patch
>
>
> It will just return the old ResultScanner and work like the AsyncPrefetchClientScanner. I think we still need this as we can not do time consuming work in the ScanObserver introduced in HBASE-16838.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)