[
https://issues.apache.org/jira/browse/HBASE-15793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-15793:
--------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.0.0
Status: Resolved (was: Patch Available)
Pushed to master branch. Thanks for the patch [~jurmous]
What is next sir? The client Async API? This is great stuff.
Just a word, you commit a patch with the JIRA issue number only. The usual
style is to include the subject as in "HBASE-15793 Port over ...". When you
don't include the subject, I'm doing git am --signoff.. then git commit --amend
to add the subject. Not important but thought you'd like to know.
> Port over AsyncCall improvements
> ---------------------------------
>
> Key: HBASE-15793
> URL: https://issues.apache.org/jira/browse/HBASE-15793
> Project: HBase
> Issue Type: Improvement
> Components: rpc
> Reporter: Jurriaan Mous
> Assignee: Jurriaan Mous
> Fix For: 2.0.0
>
> Attachments: HBASE-15793-v1.patch, HBASE-15793.patch
>
>
> Again a part of HBASE-13784 patch.
> This issue is about porting over the improvements in AsyncCall so it is a
> more flexible for usage in true async calls. It will not depend anymore on
> PayloadCarryingRpcController which is not needed in the async implementation.
> Furthermore it introduces the MessageConverter and IOExceptionConverter so
> the responses of future async calls can be converted in an easy async way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
