Hey Ryan,
Great to hear from you and welcome to Livy community!
> On 16 Apr 2019, at 18:05, Jean-Baptiste Onofré wrote:
>
> Hi Ryan,
>
> Thanks for the introduction e-mail and welcome !
>
> While ago I already proposed some potential new features to Livy. Especially
> I proposed to "decoup
Hi Jeff,
the idea is to provide kind of agnostic API and being able to leverage
Flink and eventually some Spark "flavors".
With a "Livy API", we can also imagine other engines to support Livy
(I'm thinking about Google Dataflow, etc).
Regards
JB
On 16/04/2019 18:19, Jeff Zhang wrote:
Hi JB,
Hi JB,
I notice the ticket of `decoupling` livy from spark. Which alternative
engine do you consider to adopt ?
Jean-Baptiste Onofré 于2019年4月17日周三 上午12:06写道：
> Hi Ryan,
>
> Thanks for the introduction e-mail and welcome !
>
> While ago I already proposed some potential new features to Livy.
>
Hi Ryan,
Thanks for the introduction e-mail and welcome !
While ago I already proposed some potential new features to Livy.
Especially I proposed to "decouple" Livy from Spark to be able to
interact with different execution engines.
I'm planning to move forward on Livy PoCs.
Looking forward
Hello! I haven't seen many "presentation" emails in the mailing list, but
I thought I'd introduce myself and share how we're using Livy in production.
I'm Ryan, a developer at Talend (not far from Alexey Romanenko and
Jean-Baptiste Onofre), and we've just released Talend Pipeline
Designer[1]. To
