flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kostas Tzoumas <ktzou...@apache.org>
Subject Re: Flink on Tez
Date Sun, 09 Nov 2014 09:55:32 GMT
Just to clarify, the Flink engine is not going anywhere :-) Flink should
IMO always have its own execution engine, which is currently under very
active development.

Tez and Java collections are two additional backends that users will be
able to enable depending on their needs.

On Saturday, November 8, 2014, Flavio Pompermaier <pompermaier@okkam.it>
wrote:

> Sorry for the newbie question but for me it's not clear when users
> should switch from flink runtime to tez,
> they seems to do the same thing right?
>
> On Sat, Nov 8, 2014 at 6:02 PM, Aljoscha Krettek <aljoscha@apache.org
> <javascript:;>>
> wrote:
>
> > Yes, but the beauty of it is that Flink is designed in such a way that
> > we can switch underlying runtime execution strategies and systems. Tez
> > will never be required, it's just another possible execution mode.
> >
> > Regards,
> > Aljoscha
> >
> > On Sat, Nov 8, 2014 at 12:07 PM, sirinath <sirinath1978m@gmail.com
> <javascript:;>> wrote:
> > > Great news.
> > >
> > > But as I see it if you are looking to use Flink standalone and embedded
> > best
> > > is to try to have own implementation in the long run. Besides this is
> > more
> > > optimized or created with Hadoop and related projects in mind and is
> not
> > a
> > > simple library dependency.
> > >
> > > Again great to see the initiative.
> > >
> > > (Disclaimer: I am not part of the Flink team or committeer or
> > contributor. I
> > > am just a bystander who is interested in using Flink in a particular
> way
> > /
> > > domain.)
> > >
> > > Suminda
> > >
> > >
> > >
> > > --
> > > View this message in context:
> >
> http://apache-flink-incubator-mailing-list-archive.1008284.n3.nabble.com/Flink-on-Tez-tp2407p2416.html
> > > Sent from the Apache Flink (Incubator) Mailing List archive. mailing
> > list archive at Nabble.com.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message