Sorry, coming to discussion late.
We all agreed that 2.6 would the *last* release supporting JDK6 and
hadoop-2.7 would drop support for JDK6. We could easily do 2.7 right after
2.6 (maybe with few critical bug-fixes) with the defining feature of 2.7
being *JDK7 only*. I've checked with HBase, Pig
There's actually an umbrella JIRA to track issues with JDK8
(HADOOP-11090), in case anyone missed it.
At LinkedIn we've been running our Hadoop 2.3 deployment on JDK8 for
about a month now with some mixed results. It definitely works but
there are issues, mostly around virtual memory exploding.
On Sep 17, 2014, at 2:47 AM, Steve Loughran wrote:
>
> I don't agree. Certainly the stuff I got into Hadoop 2.5 nailed down the
> filesystem binding with more tests than ever before.
FWIW, based upon my survey of JIRA, there are a lot of unit test fixes
that are only in trunk.
> But
On 15 September 2014 18:48, Allen Wittenauer wrote:
>
> It’s now September. With the passage of time, I have a lot of
> doubts about this plan and where that trajectory takes us.
>
> * The list of changes that are already in branch-2 scare the crap out of
> any risk adverse person (Hello
On Sep 15, 2014, at 11:17 AM, Colin McCabe wrote:
> On Mon, Sep 15, 2014 at 10:48 AM, Allen Wittenauer wrote:
>>
>>It’s now September. With the passage of time, I have a lot of doubts
>> about this plan and where that trajectory takes us.
>>
>> * The list of changes that are already
On Mon, Sep 15, 2014 at 10:48 AM, Allen Wittenauer wrote:
>
> It’s now September. With the passage of time, I have a lot of doubts
> about this plan and where that trajectory takes us.
>
> * The list of changes that are already in branch-2 scare the crap out of any
> risk adverse person
It’s now September. With the passage of time, I have a lot of doubts
about this plan and where that trajectory takes us.
* The list of changes that are already in branch-2 scare the crap out of any
risk adverse person (Hello to my fellow operations people!). Not only are the
number of
