hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arun Murthy <...@hortonworks.com>
Subject Re: Looking to a Hadoop 3 release
Date Tue, 03 Mar 2015 22:32:45 GMT
Awesome, looks like we can just do this in a compatible manner - nothing else on the list seems
like it warrants a (premature) major release.

Thanks Vinod.


From: Vinod Kumar Vavilapalli <vinodkv@hortonworks.com>
Sent: Tuesday, March 03, 2015 2:30 PM
To: common-dev@hadoop.apache.org
Cc: hdfs-dev@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org
Subject: Re: Looking to a Hadoop 3 release

I started pitching in more on that JIRA.

To add, I think we can and should strive for doing this in a compatible manner, whatever the
approach. Marking and calling it incompatible before we see proposal/patch seems premature
to me. Commented the same on JIRA: https://issues.apache.org/jira/browse/HADOOP-11656?focusedCommentId=14345875&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14345875.


On Mar 2, 2015, at 8:08 PM, Andrew Wang <andrew.wang@cloudera.com<mailto:andrew.wang@cloudera.com>>

Regarding classpath isolation, based on what I hear from our customers,
it's still a big problem (even after the MR classloader work). The latest
Jackson version bump was quite painful for our downstream projects, and the
HDFS client still leaks a lot of dependencies. Would welcome more
discussion of this on HADOOP-11656, Steve, Colin, and Haohui have already
chimed in.

View raw message