[
https://issues.apache.org/jira/browse/HADOOP-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544262#comment-13544262
]
Todd Lipcon commented on HADOOP-9151:
-------------------------------------
bq. Do you know how many production deployments are there on apache
2.0.2-alpha? Why they will be reluctant to upgrade their entire stack, inspite
of having chosen an alpha release and what justifies the expectation of wire
compatibility that has never been promised on Apache releases?
I don't have a scientific answer to that - haven't done any survey or anything.
Non-scientifically, I just searched the hadoop-user list for the last couple of
months and I see several questions per week pertaining to 2.x releases. I also
see a couple questions per week pertaining to NameNode HA, Federation, or other
2.0-only features. BigTop 0.5.0, which was just released, also bundles
2.0.2-alpha. So even though we've labeled it "alpha", I think it is being
treated as de facto stable by a lot of folks who have deployed it.
Cloudera hat: Again I don't have exact figures, but a significant portion of
our paying customers are running HDFS 2.0.x in production environments. You may
claim it's a bad idea because of the labeling, but in practice it has been
stable for them and aside from the labeling I think we should treat it as such.
Again, if there's a really necessary patch to address something like a security
hole, by all means let's break compatibility. But what amounts to a small code
cleanup with no advantage to our user base, why hurt them?
> 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
