It is reasonable as stephan explained. +1 from my side! 
------------------------------------------------------------------
From:Jeff Zhang <zjf...@gmail.com>
Send Time:2019年6月11日(星期二) 22:11
To:Stephan Ewen <se...@apache.org>
Cc:user <user@flink.apache.org>; dev <d...@flink.apache.org>
Subject:Re: [DISCUSS] Deprecate previous Python APIs
 +1

Stephan Ewen <se...@apache.org> 于2019年6月11日周二 下午9:30写道:

> Hi all!
>
> I would suggest to deprecating the existing python APIs for DataSet and
> DataStream API with the 1.9 release.
>
> Background is that there is a new Python API under development.
> The new Python API is initially against the Table API. Flink 1.9 will
> support Table API programs without UDFs, 1.10 is planned to support UDFs.
> Future versions would support also the DataStream API.
>
> In the long term, Flink should have one Python API for DataStream and
> Table APIs. We should not maintain multiple different implementations and
> confuse users that way.
> Given that the existing Python APIs are a bit limited and not under active
> development, I would suggest to deprecate them in favor of the new API.
>
> Best,
> Stephan
>
>

-- 
Best Regards

Jeff Zhang

Reply via email to