[
https://issues.apache.org/jira/browse/HBASE-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556520#comment-13556520
]
Devaraj Das commented on HBASE-7533:
------------------------------------
IMHO we should retain the RegionMovedException as an exception (with an
embedded Message field that basically is used for serializing the exception
fields). Maybe, have such exceptions implement an interface like PBException
that has methods that would allow them to be ser/de. Then in the RPC layer it
could do instanceof checks and ser/de such exceptions. This would prevent
parsing strings while providing PB extensibility to RPC exceptions.
Do we need to encapsulate the data within a "Response" message? Instead, if we
state in the RPC response header that there is an exception (with the
exceptionMessageType) following, we could directly serialize the exception.
Ditto for the responseBody.. We would avoid copies that way.
Thoughts?
> Write an RPC Specification for 0.96
> -----------------------------------
>
> Key: HBASE-7533
> URL: https://issues.apache.org/jira/browse/HBASE-7533
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Fix For: 0.96.0
>
> Attachments: 7533_proto_sketch.txt
>
>
> RPC format is changing for 0.96 to accomodate our protobufing all around.
> Here is a first cut. Please shred:
> https://docs.google.com/document/d/1-1RJMLXzYldmHgKP7M7ynK6euRpucD03fZ603DlZfGI/edit
--
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
