Re: Looking to a Hadoop 3 release

If classloader isolation is in place, then dependency versions can freely be upgraded as won't pollute apps space (things get trickier if there is an ON/OFF switch). On Thu, Mar 5, 2015 at 9:21 PM, Allen Wittenauer wrote: > > Is there going to be a general upgrade of dependencies? I'm thinking

Re: Looking to a Hadoop 3 release

Is there going to be a general upgrade of dependencies? I'm thinking of jetty & jackson in particular. On Mar 5, 2015, at 5:24 PM, Andrew Wang wrote: > I've taken the liberty of adding a Hadoop 3 section to the Roadmap wiki > page. In addition to the two things I've been pushing, I also looke

Re: Looking to a Hadoop 3 release

I've taken the liberty of adding a Hadoop 3 section to the Roadmap wiki page. In addition to the two things I've been pushing, I also looked through Allen's list (thanks Allen for making this) and picked out the shell script rewrite and the removal of HFTP as big changes. This would be the place to

Re: Looking to a Hadoop 3 release

I think it'll be useful to have a discussion about what else people would like to see in Hadoop 3.x - especially if the change is potentially incompatible. Also, what we expect the release schedule to be for major releases and what triggers them - JVM version, major features, the need for incompati

Re: Looking to a Hadoop 3 release

Sorry, outlook dequoted Alejandros's comments. Let me try again with his comments in italic and proofreading of mine On 05/03/2015 13:59, "Steve Loughran" mailto:ste...@hortonworks.com>> wrote: On 05/03/2015 13:05, "Alejandro Abdelnur" mailto:tuc...@gmail.com>> wrote

Re: Looking to a Hadoop 3 release

On 05/03/2015 13:05, "Alejandro Abdelnur" mailto:tuc...@gmail.com>> wrote: IMO, if part of the community wants to take on the responsibility and work that takes to do a new major release, we should not discourage them from doing that. Having multiple major branches active is a standard practic

Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches

Tx for the feedback! Let's continue on JIRA, but I'd definitely welcome as much help as is available. Thanks, +Vinod On Mar 4, 2015, at 3:30 PM, Zhijie Shen wrote: > +1. It¹s really helpful for branch development. To continue Karthik¹s > point, is it good make pre-commit testing against branch

Re: 2.7 status

The 2.7 blocker JIRA went down and going back up again, we will need to converge. Unless I see objections, I plan to cut a branch this weekend and selectively filter stuff in after that in the interest of convergence. Thoughts welcome! Thanks, +Vinod On Mar 1, 2015, at 11:58 AM, Arun Murthy

Re: Looking to a Hadoop 3 release

I'm OK with a 3.0.0 release as long as we are minimizing the pain of maintaining yet another release line and conscious of the incompatibilities going into that release line. For the former, I would really rather not see a branch-3 cut so soon.  It's yet another line onto which to cherry-pick, a

Re: Looking to a Hadoop 3 release

IMO, if part of the community wants to take on the responsibility and work that takes to do a new major release, we should not discourage them from doing that. Having multiple major branches active is a standard practice. This time around we are not replacing the guts as we did from Hadoop 1 to H

Re: Looking to a Hadoop 3 release

The 'resistance' is not so much about a new major release, more so about the content and the roadmap of the release. Other than the two specific features raised (the need for breaking compat for them is something that I am debating), I haven't seen a roadmap of branch-3 about any more features

Re: Looking to a Hadoop 3 release

Moving to JDK8 involves a lot of things (1) Get Hadoop apps to be able to run on JDK8 and chose JDK8 language features. This is already possible with the decoupling of apps from the platform. (2) Get the platform to run on JDK8. This can be done so that we can run Hadoop on both JDK8 and JDK7

Re: Looking to a Hadoop 3 release

On Mon, Mar 2, 2015 at 11:04 PM, Konstantin Shvachko wrote: > 2. If Hadoop 3 and 2.x are meant to exist together, we run a risk to > manifest split-brain behavior again, as we had with hadoop-1, hadoop-2 and > other versions. If that somehow beneficial for commercial vendors, which I > don't see h

Re: Looking to a Hadoop 3 release

Thanks all. There is an open issue HDFS-6962 (ACLs inheritance conflicts with umaskmode), for which the incompatibility appears to make it not suitable for 2.x and it's targetted 3.0, please see: https://issues.apache.org/jira/browse/HDFS-6962?focusedCommentId=14335418&page=com.atlassian.jira.plu

Hadoop-Mapreduce-trunk - Build # 2073 - Failure

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2073/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 31198 lines...] Tests run: 520, Failures: 0, Errors:

Hadoop-Mapreduce-trunk-Java8 - Build # 123 - Still Failing

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/123/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10611 lines...] Tests run: 521, Failures: 2, Er