[
https://issues.apache.org/jira/browse/HBASE-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542245#comment-13542245
]
stack commented on HBASE-5620:
------------------------------
[~jxiang] I've been experimenting over in HBASE-6521 RpcController seems
pretty useless though experimenting I ended up using it to carry extra payload
in and out of the method on the server-side, not in client as here.
VersionedProtocol is going away. We could just resort to raw
BlockingInterfaces everywhere instead (though I do not think this will be work
too cleanly since there is no common ancestor to BlockingInterface). We could
redefine all methods to be what is in BlockingInterface minus this
rpccontroller stuff -- or, as you have it, just use what protoc generates as
the Interface and be clear that the rpccontroller goes unused.
I think we should go w/ the latter approach. Use raw blockinginterface where
we can being clear rpccontroller is an unused field.
Thanks for the answers Jimmy.
> Convert the client protocol of HRegionInterface to PB
> -----------------------------------------------------
>
> Key: HBASE-5620
> URL: https://issues.apache.org/jira/browse/HBASE-5620
> Project: HBase
> Issue Type: Sub-task
> Components: IPC/RPC, master, migration, regionserver
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Fix For: 0.96.0
>
> Attachments: hbase-5620-sec.patch, hbase-5620_v3.patch,
> hbase-5620_v4.patch, hbase-5620_v4.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
