[
https://issues.apache.org/jira/browse/HBASE-16505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455975#comment-15455975
]
Yu Li commented on HBASE-16505:
-------------------------------
[~yangzhe1991] Just to confirm, that in the current design, I assume the usage
would be like:
# Initialize a {{RegionOperationContext}} instance
# Start a new thread (or hand to Netty thread) to call the AsyncRegion with
this RegionOperationContext
# In the main thread, use {{RegionOperationContext#getResult}} to get the
result asynchronously, rather than blocking and wait
Correct?
When talking about "asynchronous non-blocking way", I just meant to emphasize
*non-blocking*. Or say it's not like the current AsyncRpcClient that although
we hand over the request to netty which does things in an async way, we will
wait for the result (rather than using callback/listener) so it's still
blocking mode.
> 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
> Attachments: HBASE-16505-v1.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)
