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'
x27;t see the difference?
>>
>> Arun
>>
>>
>> From: Colin P. McCabe
>> Sent: Monday, March 09, 2015 3:05 PM
>> To: hdfs-...@hadoop.apache.org
>> Cc: mapreduce-...@hadoop.apache.org; common-dev@hadoop.apache.o
.org; common-dev@hadoop.apache.org;
> yarn-...@hadoop.apache.org
> Subject: Re: Hadoop 3.x: what about shipping trunk as a 2.x release in 2015?
>
> Java 7 will be end-of-lifed in April 2015. I think it would be unwise
> to plan a new Hadoop release against a version of Java that i
Between this and the other thread, I’m seeing:
* companies that were forced to make internal forks because their
patches were ignored are now considered the deciders for whether we move forward
* 5 years since the last branch off of trunk is considered ‘soon’
* M
On 09/03/2015 15:56, "Andrew Wang" wrote:
>I find this proposal very surprising. We've intentionally deferred
>incompatible changes to trunk, because they are incompatible and do not
>belong in a minor release. Now we are supposed to blur our eyes and
>release
>these changes anyway? I don't see
I find this proposal very surprising. We've intentionally deferred
incompatible changes to trunk, because they are incompatible and do not
belong in a minor release. Now we are supposed to blur our eyes and release
these changes anyway? I don't see this ending well.
One higher-level goal we should
nt: Monday, March 09, 2015 3:05 PM
To: hdfs-...@hadoop.apache.org
Cc: mapreduce-...@hadoop.apache.org; common-dev@hadoop.apache.org;
yarn-...@hadoop.apache.org
Subject: Re: Hadoop 3.x: what about shipping trunk as a 2.x release in 2015?
Java 7 will be end-of-lifed in April 2015. I think it would
Java 7 will be end-of-lifed in April 2015. I think it would be unwise
to plan a new Hadoop release against a version of Java that is almost
obsolete and (soon) no longer receiving security updates. I think
people will be willing to roll out a new version of Java for Hadoop
3.x.
Similarly, the wh
Steve,
From: Steve Loughran
Sent: Monday, March 09, 2015 2:15 PM
To: mapreduce-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
common-dev@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Hadoop 3.x: what about shipping trunk as a 2.x release in
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's dev pull
for this, there's ops pull against this: people are st
11 matches
Mail list logo
