On Mar 10, 2015, at 12:40 PM, Karthik Kambatla wrote:
>
> Are we okay with breaking other forms of compatibility for Hadoop-3, like
> behavior, dependencies, JDK, classpath, environment? I think so. Are we
> okay with breaking these forms of compatibility in future Hadoop-2.x?
> Likely not. Doe
On Mon, Mar 9, 2015 at 2:15 PM, Steve Loughran
wrote:
>
> If 3.x is going to be Java 8 & not backwards compatible, I don't expect
> anyone wanting to use this in production until some time deep into 2016.
>
> Issue: JDK 8 vs 7
>
> It will require Hadoop clusters to move up to Java 8. While there'
Anubhav Dhoot created MAPREDUCE-6272:
Summary: NodeManager should use directory other than tmp for
extracting and loading leveldbjni
Key: MAPREDUCE-6272
URL: https://issues.apache.org/jira/browse/MAPREDUCE-627
Hi Arun,
Not all changes which are incompatible can be "fixed"-- sometimes an
incompatibility is a necessary part of a change. For example, taking
a really old library dependency with known security issues off the
CLASSPATH will create incompatibilities, but it's also necessary. A
minimum JDK ve
Er, that should read "as Allen commented" C.
On Tue, Mar 10, 2015 at 11:55 AM, Colin P. McCabe wrote:
> Hi Arun,
>
> Not all changes which are incompatible can be "fixed"-- sometimes an
> incompatibility is a necessary part of a change. For example, taking
> a really old library dependency with
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2078/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 31273 lines...]
Tests run: 522, Failures: 1, Errors
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/128/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 10659 lines...]
Tests run: 522, Failures: 2, E
