Mailing-List: contact dev-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: Dripping the Flink-on-Tez code for Flink 1.0
From: Ufuk Celebi <uce@apache.org>
In-Reply-To: 
 <CALuGr6b0eE8+6nDnMgm-Fbd+B5dSc9GcjELHAkTGqn5wP0RHhw@mail.gmail.com>
Date: Thu, 14 Jan 2016 19:53:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E9144F9-6D41-48C6-9773-EF7748BFC118@apache.org>
References: 
 <CANC1h_sL0JzRw4r2oWbSSVwc8Ooa4xvFswR-Cz5hQJ9SfTVKBw@mail.gmail.com>
 <CAGWx-_soux_+ven5Spkx3XxKNcOqUqqz8Gge7_LJ0jbMoex0Fg@mail.gmail.com>
 <CAGWx-_vm10tW3Peqxhf-COYKLXprA0-KMCq=PqYTU4N2YJfJiw@mail.gmail.com>
 <5DC91774-00B7-4CEA-A913-2063FCEF8677@apache.org>
 <CAC27z=N5ynFjFq5_nKqu9+BquNkyDa4MeG4D==+jQ1BKcTe=og@mail.gmail.com>
 <CAAdrtT2whVBubgaCFU=sHa6uq2iEuyft_JZ_5r+ikd1yTzoJCg@mail.gmail.com>
 <CANC1h_sW0oNHkZ5xRRq-z2wB=bY8Y6QiFi+JR+M2=Zw2gJPKag@mail.gmail.com>
 <CALuGr6b0eE8+6nDnMgm-Fbd+B5dSc9GcjELHAkTGqn5wP0RHhw@mail.gmail.com>
To: dev@flink.apache.org

I=E2=80=99ve created an issue [1] and closed all other Tez issues.

[1] https://issues.apache.org/jira/browse/FLINK-3235

> On 11 Jan 2016, at 02:52, Henry Saputra <henry.saputra@gmail.com> =
wrote:
>=20
> +1
>=20
> I am always for simplifying our code base when possible.
>=20
>=20
>=20
> On Sunday, January 10, 2016, Stephan Ewen <sewen@apache.org> wrote:
>=20
>> I was typing with fat fingers again. Meant "dropping code" of course, =
not
>> "dripping" ;-)
>>=20
>> On Sun, Jan 10, 2016 at 11:55 AM, Fabian Hueske <fhueske@gmail.com
>> <javascript:;>> wrote:
>>=20
>>> +1
>>>=20
>>> 2016-01-08 17:35 GMT+01:00 Till Rohrmann <trohrmann@apache.org
>> <javascript:;>>:
>>>=20
>>>> +1 since it increase maintainability of the code base if it is not
>> really
>>>> used and thus removed.
>>>>=20
>>>> On Fri, Jan 8, 2016 at 5:33 PM, Ufuk Celebi <uce@apache.org
>> <javascript:;>> wrote:
>>>>=20
>>>>> +1
>>>>>=20
>>>>> I wanted to make a similar proposal.
>>>>>=20
>>>>> =E2=80=93 Ufuk
>>>>>=20
>>>>>> On 08 Jan 2016, at 17:03, Kostas Tzoumas <ktzoumas@apache.org
>> <javascript:;>>
>>> wrote:
>>>>>>=20
>>>>>> for clarification, I was talking about dropping the code, I am
>> unsure
>>>>> about
>>>>>> the consequences of dripping code :-)
>>>>>>=20
>>>>>> On Fri, Jan 8, 2016 at 4:57 PM, Kostas Tzoumas <
>> ktzoumas@apache.org <javascript:;>>
>>>>> wrote:
>>>>>>=20
>>>>>>> +1 from my side
>>>>>>>=20
>>>>>>> Flink on Tez never got a lot of user traction. It served well as =
a
>>>>>>> prototype of "this is possible", but since the core =
functionality
>>> will
>>>>> be
>>>>>>> subsumed by making Flink on YARN resource elastic, I don't see =
any
>>>>> reason
>>>>>>> we should have it as part of the Flink codebase.
>>>>>>>=20
>>>>>>> Best,
>>>>>>> Kostas
>>>>>>>=20
>>>>>>> On Fri, Jan 8, 2016 at 4:43 PM, Stephan Ewen <sewen@apache.org
>> <javascript:;>>
>>>> wrote:
>>>>>>>=20
>>>>>>>> Hi all!
>>>>>>>>=20
>>>>>>>> Currently, Flink has a module to run batch program code on Tez
>>> rather
>>>>> than
>>>>>>>> Flink's own distributed execution engine.
>>>>>>>>=20
>>>>>>>> I would suggest that we drop this code for the next release =
(1.0)
>>> as
>>>>> part
>>>>>>>> of a code consolidation:
>>>>>>>>=20
>>>>>>>> - There seems little in both the Flink and the Tez community to
>>> use
>>>>> and
>>>>>>>> expand this functionality.
>>>>>>>>=20
>>>>>>>> - The original motivation (better exploit resource elasticity =
in
>>>> YARN)
>>>>>>>> will no longer be valid in the near future. I am re-working the
>>> YARN
>>>>>>>> integration currently to make it more elastic and make it
>> possible
>>> to
>>>>> run
>>>>>>>> Flink on Mesos.
>>>>>>>>=20
>>>>>>>> - The Flink-on-Tez code is rather POC status. Large scale
>> testing
>>> it
>>>>> and
>>>>>>>> making adding all missing features will take more effort than
>>> making
>>>>>>>> Flink's own YARN integration resource elastic.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Please let me know what you think!
>>>>>>>> Especially @Kostas, since you wrote the initial POC, I'd be
>>>> interested
>>>>> in
>>>>>>>> your opinion.
>>>>>>>>=20
>>>>>>>> Greetings,
>>>>>>>> Stephan
>>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>=20
>>>>>=20
>>>>=20
>>>=20
>>=20