+1
Thanks Kostas for pushing this.
Thanks,
Biao /'bɪ.aʊ/
On Thu, 15 Aug 2019 at 16:03, Kostas Kloudas wrote:
> Thanks a lot for the quick response!
> I will consider the Flink Accepted and will start working on it.
>
> Cheers,
> Kostas
>
> On Thu, Aug 15, 2019 at 5:29 AM SHI Xiaogang
>
Thanks a lot for the quick response!
I will consider the Flink Accepted and will start working on it.
Cheers,
Kostas
On Thu, Aug 15, 2019 at 5:29 AM SHI Xiaogang wrote:
>
> +1
>
> Glad that programming with flink becomes simpler and easier.
>
> Regards,
> Xiaogang
>
> Aljoscha Krettek
+1
Glad that programming with flink becomes simpler and easier.
Regards,
Xiaogang
Aljoscha Krettek 于2019年8月14日周三 下午11:31写道：
> +1 (for the same reasons I posted on the other thread)
>
> > On 14. Aug 2019, at 15:03, Zili Chen wrote:
> >
> > +1
> >
> > It could be regarded as part of Flink
+1 (for the same reasons I posted on the other thread)
> On 14. Aug 2019, at 15:03, Zili Chen wrote:
>
> +1
>
> It could be regarded as part of Flink client api refactor.
> Removal of stale code paths helps reason refactor.
>
> There is one thing worth attention that in this thread[1] Thomas
+1
It could be regarded as part of Flink client api refactor.
Removal of stale code paths helps reason refactor.
There is one thing worth attention that in this thread[1] Thomas
suggests an interface with a method return JobGraph based on the
fact that REST API and in per job mode actually
+1
Cheers,
Till
On Wed, Aug 14, 2019 at 1:50 PM Stephan Ewen wrote:
> +1
>
> the "main" method is the overwhelming default. getting rid of "two ways to
> do things" is a good idea.
>
> On Wed, Aug 14, 2019 at 1:42 PM Kostas Kloudas wrote:
>
> > Hi all,
> >
> > As discussed in [1] , the
+1
the "main" method is the overwhelming default. getting rid of "two ways to
do things" is a good idea.
On Wed, Aug 14, 2019 at 1:42 PM Kostas Kloudas wrote:
> Hi all,
>
> As discussed in [1] , the Program interface seems to be outdated and
> there seems to be
> no objection to remove it.
>
>
