Re: Flink on Tez

Why don't you have an internal engine which addresses both the concerns raised than one over the other. Also configuration can help towards which type of optimisation is done in cases where things are mutually exclusive. -- View this message in context: http://apache-flink-incubator-mailing-lis

Re: beginner

Hi Navya, the best way to get started contributing to Flink is first to familiarise yourself with Flink by reading through the documentation here: http://flink.incubator.apache.org/docs/0.7-incubating/ and then to read the how to contribute article here: http://flink.incubator.apache.org/how-to-co

Re: beginner

Hello. There is a help article for new contributor. http://flink.incubator.apache.org/how-to-contribute.html If you read this first, you can learn contributing to Flink project. — Chiwan Park (Sent with iPhone) > On Nov 9, 2014, at

beginner

Hello, I want to learn contributing to Open SOURCE through your organisation.Can somebody please help me out? Thank you

Re: Flink on Tez

This was kind of the substance of the same conversation that happened about Spark on Tez, which looks like it was rejected (https://issues.apache.org/jira/browse/SPARK-3561): - Committing to an SPI interface is hard and imposes its own design and runtime limitations - Fragments / forks efforts acr

Re: Flink on Tez

Thanks Kostas fir the reply. I've already read your first post and what is not fully clear to me is the technical motivation of. "Tez follows design choices that are geared towards resource elasticity, whereas the design choices behind Flink's engine are geared more towards low latency querying and

Re: Flink on Tez

Flavio, see my first post in this thread. If these differences are fine print for your application/requirements, then yes, both backends will do the same thing (distribute computation). In that case, the suggestion would be to use Flink in the normal way, as it is much more mature implementation-w

Re: Flink on Tez

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, Novemb