[
https://issues.apache.org/jira/browse/HADOOP-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537518#comment-13537518
]
Suresh Srinivas commented on HADOOP-9151:
-----------------------------------------
bq. As far as I know we have not broken RPC or API compatibility at all since
2.0.0, and I would be against any case where we do (not just this one).
We have not broken API compatibility in a long time. Even though RPC
compatibility is not broken, there have been many changes marked as
incompatible (I counted 6 of them). Just because incompatible changes have not
been done in RPC does not mean it cannot be done.
bq. As for the labeling of alpha, I have been arguing against calling it alpha
for several months
The reason of having alpha tag is so that we do not have to provide the
stricter guarantees of a GA release. I am glad that we have retained it so far,
so that these kind of changes can happen.
bq. In the spirit of full disclosure: wearing my Cloudera hat, we have a
distribution based on the Hadoop 2 code line. We are not going to break wire
compatibility within minor updates of this distribution. So, if branch-2 breaks
compatibility, then our distro will become incompatible with branch-2, which is
no good.
We are talking about Apache 2.0.x-alpha release here. How CDH manages its
distribution, backward compatibility does not guide how Apache releases are
done or what goes into Apache releases. The fact that you chose include a
content that is not in trunk or decided to tag a release in some other way
should not put constraints on the Apache releases. Wearing my Apache hat on, if
this is the main reason for -1, then it has no merit.
If there was no issue to CDH distribution, would you have objected to this
change?
I would like others to comment on why a vendor's distribution or compatibility
to it should put artificial constraints in Apache.
> 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
