[
https://issues.apache.org/jira/browse/HADOOP-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537613#comment-13537613
]
Suresh Srinivas commented on HADOOP-9151:
-----------------------------------------
bq. So, given that I already consider HDFS to be "stable", and know people
running this branch in production scenarios where a rolling upgrade is
required, I would make the same argument that we should not break compatibility.
You may consider it to be "stable". But the release is called 2.0.2-"alpha".
Before calling it GA, I was planning to run through a checklist to make sure
our wire compatibility story is rock solid. That is what is happening some of
the jiras that are being filed now.
bq. If this issue were a case of a big performance improvement, or a security
issue, or even a feature improvement, I would weigh it stronger
While these are compelling reasons for you, getting rid of writable in
serialized rpc request and response is equally important. I and Sanjay have
spent quite a lot of time on this. Seeing it completed before GA is a good goal.
> 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
