[ 
https://issues.apache.org/jira/browse/HADOOP-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538753#comment-13538753
 ] 

Arun C Murthy commented on HADOOP-9151:
---------------------------------------

Thanks, I appreciate you being upfront - but it doesn't change the merits of 
your veto. As others have pointed out, you are welcome to continue shipping CDH 
without these changes.

The 'alpha'/'beta' tags are meant to be a warning to end-users about the 
stability of the software (apis, wire-protocols etc.) and users can make their 
own decisions. We've discussed this many times for very good reasons - for e.g. 
the PB-based HDFS protocols are very raw (~12 months old at this point v/s 
Writables' RPC viz. nearly 4-5yrs now) and it's not surprising we hit these 
issues, there may be further down the road.

Also, it isn't true that the discussion was limited to YARN, see the link I 
posted above w.r.t HDFS from Suresh:  http://s.apache.org/qQp. I'm pretty sure 
you've ascribed to above views too (w.r.t changing wire-protocols on HDFS etc.) 
- here is your own view that HDFS protocols aren't 'baked' yet: 
http://s.apache.org/PRh

Having said that, I agree we maybe overblowing the current issue.

However, we might have to do more changes of this nature in the future (maybe 
major bugs or new features etc. before hadoop-2 hits 'stable') and I really 
hope you won't be vetoing further development on grounds of 'CDH 
compatibility'. 
                
> 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

Reply via email to