Hi All,
Thank Aljoscha for further spitting up topics.
I will start separate threads on each topic which you propose.
Best,
Haibo
Aljoscha Krettek-2 wrote
> Hi All,
>
> this is a great discussion! (I have some thoughts on most of the topics
> but I'll wait for the separate discussion threads
Hi All,
this is a great discussion! (I have some thoughts on most of the topics but
I'll wait for the separate discussion threads)
@Haibo Will you start a separate threads? I think the separate discussion
topics would be (based on Stephans mail but further split up):
1. What should the API sta
Hi all
Glad to see the discussion, we are now designing to enhance the scheduling
of batch job, a unified api will help a lot.
Haibo Sun 于2018年12月5日周三 下午4:45写道：
> Hi all,
>
> Thank Kurt, you see more benefits of the unification than I do.
>
> I quite agree Kurt's views. DataStream, DataSet and T
Hi all,
Thank Kurt, you see more benefits of the unification than I do.
I quite agree Kurt's views. DataStream, DataSet and Table are remained
independent for now, and subsumed DataSet in data stream in the future. The
collection execution mode is replaced by mini cluster. The high-level
semantic
gt; they are unified into one stack, the batch jobs can also get benefits
> from
> > all the improvements. I think it is a very big work but worth doing, left
> > some concerns:
> >
> > 1. The current job graph generation for batch covers complicated
> > optimization such as cost-based estimate, plan etc. Would this part also
s input selection while reading. I acknowledge these roles for
> special batch scenarios, but they seem not the blocker for unification
> motivation, because current batch jobs can also work without these
> improvements. So the further improvments can be separated into individual
> topics after we
s after we reaching the unification of stream and batch firstly.
Best,
Zhijiang
--
发件人：孙海波 mailto:sunhaib...@163.com>>
发送时间：2018年12月3日(星期一) 10:52
收件人：dev mailto:dev@flink.apache.org>>
主 题：[DISCUSS] Unified Core API for Strea
because current batch jobs can also work without these
> improvements. So the further improvments can be separated into individual
> topics after we reaching the unification of stream and batch firstly.
> >
> >Best,
> >Zhijiang
> >
> >
> >-
e reaching the
>unification of stream and batch firstly.
>
>Best,
>Zhijiang
>
>
>----------------------
>发件人：孙海波
>发送时间：2018年12月3日(星期一) 10:52
>收件人：dev
>主 题：[DISCUSS] Unified Core API for Streaming and Batch
>
>Hi all,
>This post proposes unified core API for Streaming and Bat
Hi Haibo,
Thank you for this great proposal！
Flink is a unified computing engine. It has been unified at the TableAPI
and SQLAPI levels (not yet complete). It's greate If we can unify the
DataSet API and DataStream API.
I also want to convert to StreamTransformation in the SQL and Table API,
bec
unification of stream and batch firstly.
Best,
Zhijiang
--
发件人：孙海波
发送时间：2018年12月3日(星期一) 10:52
收件人：dev
主 题：[DISCUSS] Unified Core API for Streaming and Batch
Hi all,
This post proposes unified core API for Streaming and Batch.
Currently
Hi all,
This post proposes unified core API for Streaming and Batch.
Currently DataStream and DataSet adopt separated compilation processes,
execution tasks
and basic programming models in the runtime layer, which complicates the system
implementation.
We think that batch jobs can be processed
12 matches
Mail list logo
