[
https://issues.apache.org/jira/browse/HBASE-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683537#comment-15683537
]
Duo Zhang commented on HBASE-17141:
-----------------------------------
[~stack] [~carp84] FYI.
And for sharing the same interface for the two implementation, as I said in
HBASE-16984, I'm little nervous about the {{ScanResultConsumer}} as it exposes
some implementation details to the user(heartbeat). Yeah for ResultScanner we
also expose the renewLease method to user but I do not think it is a good
idea...
So I propose that we keep the two interfaces for now, and revisit it after we
implement most features for AsyncTable. If scan is still the only difference
between these two interfaces, then let's think about how to unify them.
What do you guys think?
Thanks..
> Introduce a more user-friendly implementation of AsyncTable
> -----------------------------------------------------------
>
> Key: HBASE-17141
> URL: https://issues.apache.org/jira/browse/HBASE-17141
> Project: HBase
> Issue Type: Sub-task
> Components: asyncclient, Client
> Affects Versions: 2.0.0
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0
>
> Attachments: HBASE-17141.patch
>
>
> The current AsyncTable implementation exposes the low level details so it is
> safe for normal users. If they do some time consuming work in the callback or
> consumer logic then the whole rpc connection will be blocked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
