[
https://issues.apache.org/jira/browse/HADOOP-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537323#comment-13537323
]
Suresh Srinivas commented on HADOOP-9151:
-----------------------------------------
bq. I'd be +1 on this for 3.0 but not for branch-2, unless you can figure out
some way of maintaining a compatibility path.
The main reason why we started the protobuf work was to make sure once we
declare 2.0 as GA we will do the needed complex code to maintain the
compatibility. So breaking compatibility for 3.0 should not be necessary.
I understand that it could be messy for downstream projects. But that is what
an alpha release tag is meant to indicate. BTW since 2.0.0-alpha we have had
many incompatible changes as well. Granted, they may not affect HBase, but does
affect other folks some way or the other. BTW I have reflected same sentiments
in the discussion thread of making 2.0.0 beta as well. If we are going to make
these kinds of changes even harder to make with the beta tag, I am reluctant to
change the tag.
> Include RPC error info in RpcResponseHeader instead of sending it separately
> ----------------------------------------------------------------------------
>
> Key: HADOOP-9151
> URL: https://issues.apache.org/jira/browse/HADOOP-9151
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
> Attachments: HADOOP-9151.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
