[
https://issues.apache.org/jira/browse/HBASE-16505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489807#comment-15489807
]
Phil Yang commented on HBASE-16505:
-----------------------------------
Changing api of Region results in too many following changes just adding a new
param and use CompletableFuture to get the return value. So my plan is use a
RegionBase interface to cover all methods which will not have new version in
current Region, eg. getRegionInfo(), and use two interface extend it: an
interface which is same as now and a new one returning CompletableFuture,
although it is still blocking at first. The first interface may be called
BlockingRegion and marked as @Deprecated, and the second one call Region and
expected to be used by default. In future we will change the implementation
into fully non-blocking which we can discuss in HBASE-16583 (maybe not SEDA,
but we indeed need async)
[~enis] [~Apache9] What do you think? Thanks.
> Add AsyncRegion interface to pass deadline and support async operations
> -----------------------------------------------------------------------
>
> Key: HBASE-16505
> URL: https://issues.apache.org/jira/browse/HBASE-16505
> Project: HBase
> Issue Type: Sub-task
> Reporter: Phil Yang
> Assignee: Phil Yang
> Fix For: 2.0.0
>
> Attachments: HBASE-16505-branch-1-v1.patch, HBASE-16505-v1.patch,
> HBASE-16505-v10.patch, HBASE-16505-v10.patch, HBASE-16505-v2.patch,
> HBASE-16505-v3.patch, HBASE-16505-v4.patch, HBASE-16505-v5.patch,
> HBASE-16505-v6.patch, HBASE-16505-v7.patch, HBASE-16505-v8.patch,
> HBASE-16505-v9.patch
>
>
> If we want to know the correct setting of timeout in read/write path, we need
> add a new parameter in operation-methods of Region.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
