[
https://issues.apache.org/jira/browse/HBASE-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551453#comment-13551453
]
Elliott Clark commented on HBASE-7533:
--------------------------------------
The Union message types are structured after
https://developers.google.com/protocol-buffers/docs/techniques#union.
We should move the enum out of the Request/Response messages. That will clean
some things up a little.
As far as the exception being in the enum, my thinking was as follows:
* For multi we could say what type the response should be.
* Then if there's an exception put that in the exceptions field.
* If there was a partial result it could still go in the result field.
This would allow us to give partial results (a new feature for the 0.98ish time
frame). It would also allow us to just give the features that we have
currently.
> 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
>
>
> 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
