I created a Jira for this: https://issues.apache.org/jira/browse/FLINK-2643
On Fri, 4 Sep 2015 at 13:01 Matthias J. Sax wrote:
> +1 for dropping
>
> On 09/04/2015 11:04 AM, Maximilian Michels wrote:
> > +1 for dropping Hadoop 2.2.0 binary and source-compatibility. The
> > release is hardly used
+1 for dropping
On 09/04/2015 11:04 AM, Maximilian Michels wrote:
> +1 for dropping Hadoop 2.2.0 binary and source-compatibility. The
> release is hardly used and complicates the important high-availability
> changes in Flink.
>
> On Fri, Sep 4, 2015 at 9:33 AM, Stephan Ewen wrote:
>> I am good
+1 for dropping Hadoop 2.2.0 binary and source-compatibility. The
release is hardly used and complicates the important high-availability
changes in Flink.
On Fri, Sep 4, 2015 at 9:33 AM, Stephan Ewen wrote:
> I am good with that as well. Mind that we are not only dropping a binary
> distribution
I am good with that as well. Mind that we are not only dropping a binary
distribution for Hadoop 2.2.0, but also the source compatibility with 2.2.0.
Lets also reconfigure Travis to test
- Hadoop1
- Hadoop 2.3
- Hadoop 2.4
- Hadoop 2.6
- Hadoop 2.7
On Fri, Sep 4, 2015 at 6:19 AM, Chiwan
+1 for dropping Hadoop 2.2.0
Regards,
Chiwan Park
> On Sep 4, 2015, at 5:58 AM, Ufuk Celebi wrote:
>
> +1 to what Robert said.
>
> On Thursday, September 3, 2015, Robert Metzger wrote:
> I think most cloud providers moved beyond Hadoop 2.2.0.
> Google's Click-To-Deploy is on 2.4.1
> AWS EMR i
+1 to what Robert said.
On Thursday, September 3, 2015, Robert Metzger wrote:
> I think most cloud providers moved beyond Hadoop 2.2.0.
> Google's Click-To-Deploy is on 2.4.1
> AWS EMR is on 2.6.0
>
> The situation for the distributions seems to be the following:
> MapR 4 uses Hadoop 2.4.0 (curr
I think most cloud providers moved beyond Hadoop 2.2.0.
Google's Click-To-Deploy is on 2.4.1
AWS EMR is on 2.6.0
The situation for the distributions seems to be the following:
MapR 4 uses Hadoop 2.4.0 (current is MapR 5)
CDH 5.0 uses 2.3.0 (the current CDH release is 5.4)
HDP 2.0 (October 2013)
While working on high availability (HA) for Flink's YARN execution I
stumbled across some limitations with Hadoop 2.2.0. From version 2.2.0 to
2.3.0, Hadoop introduced new functionality which is required for an
efficient HA implementation. Therefore, I was wondering whether there is
actually a need
