Re: [DISCUSS] Deprecate previous Python APIs

[Chesnay Schepler]

I have created a JIRA 
 and PR 
 for removing the Python APIs.


On 11/06/2019 15:30, Stephan Ewen wrote:

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

Re: [DISCUSS] Deprecate previous Python APIs

[jincheng sun]

+1 for removing and we can try our best to enrich the new Python API.

Cheers,
Jincheng

Yu Li  于2019年6月14日周五 下午6:42写道：

> +1 on removing plus an explicit NOTE thread, to prevent any neglection due
> to the current title (deprecation).
>
> Best Regards,
> Yu
>
>
> On Fri, 14 Jun 2019 at 18:09, Stephan Ewen  wrote:
>
>> Okay, so we seem to have consensus for at least deprecating them, with a
>> suggestion to even directly remove them.
>>
>> A previous survey also brought no users of that python API to light [1]
>> I am inclined to go with removing.
>> Typically, deprecation is the way to go, but we could make an exception
>> and expedite things here.
>>
>> [1]
>> https://lists.apache.org/thread.html/348366080d6b87bf390efb98e5bf268620ab04a0451f8459e2f466cd@%3Cdev.flink.apache.org%3E
>>
>>
>> On Wed, Jun 12, 2019 at 2:37 PM Chesnay Schepler 
>> wrote:
>>
>>> I would just remove them. As you said, there are very limited as to what
>>> features they support, and haven't been under active development for
>>> several releases.
>>>
>>> Existing users (if there even are any) could continue to use older
>>> version against newer releases. It's is slightly more involved than for
>>> say, flink-ml, as you also have to copy the start-scripts (or figure out
>>> how to use the jars yourself), but it is still feasible and can be
>>> documented in the release notes.
>>>
>>> On 11/06/2019 15:30, Stephan Ewen wrote:
>>> > 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
>>> >
>>>
>>>

Re: [DISCUSS] Deprecate previous Python APIs

[Yu Li]

+1 on removing plus an explicit NOTE thread, to prevent any neglection due
to the current title (deprecation).

Best Regards,
Yu


On Fri, 14 Jun 2019 at 18:09, Stephan Ewen  wrote:

> Okay, so we seem to have consensus for at least deprecating them, with a
> suggestion to even directly remove them.
>
> A previous survey also brought no users of that python API to light [1]
> I am inclined to go with removing.
> Typically, deprecation is the way to go, but we could make an exception
> and expedite things here.
>
> [1]
> https://lists.apache.org/thread.html/348366080d6b87bf390efb98e5bf268620ab04a0451f8459e2f466cd@%3Cdev.flink.apache.org%3E
>
>
> On Wed, Jun 12, 2019 at 2:37 PM Chesnay Schepler 
> wrote:
>
>> I would just remove them. As you said, there are very limited as to what
>> features they support, and haven't been under active development for
>> several releases.
>>
>> Existing users (if there even are any) could continue to use older
>> version against newer releases. It's is slightly more involved than for
>> say, flink-ml, as you also have to copy the start-scripts (or figure out
>> how to use the jars yourself), but it is still feasible and can be
>> documented in the release notes.
>>
>> On 11/06/2019 15:30, Stephan Ewen wrote:
>> > 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
>> >
>>
>>

Re: [DISCUSS] Deprecate previous Python APIs

[Stephan Ewen]

Okay, so we seem to have consensus for at least deprecating them, with a
suggestion to even directly remove them.

A previous survey also brought no users of that python API to light [1]
I am inclined to go with removing.
Typically, deprecation is the way to go, but we could make an exception and
expedite things here.

[1]
https://lists.apache.org/thread.html/348366080d6b87bf390efb98e5bf268620ab04a0451f8459e2f466cd@%3Cdev.flink.apache.org%3E


On Wed, Jun 12, 2019 at 2:37 PM Chesnay Schepler  wrote:

> I would just remove them. As you said, there are very limited as to what
> features they support, and haven't been under active development for
> several releases.
>
> Existing users (if there even are any) could continue to use older
> version against newer releases. It's is slightly more involved than for
> say, flink-ml, as you also have to copy the start-scripts (or figure out
> how to use the jars yourself), but it is still feasible and can be
> documented in the release notes.
>
> On 11/06/2019 15:30, Stephan Ewen wrote:
> > 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
> >
>
>

Re: [DISCUSS] Deprecate previous Python APIs

[Chesnay Schepler]

I would just remove them. As you said, there are very limited as to what 
features they support, and haven't been under active development for 
several releases.


Existing users (if there even are any) could continue to use older 
version against newer releases. It's is slightly more involved than for 
say, flink-ml, as you also have to copy the start-scripts (or figure out 
how to use the jars yourself), but it is still feasible and can be 
documented in the release notes.


On 11/06/2019 15:30, Stephan Ewen wrote:

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

Re: [DISCUSS] Deprecate previous Python APIs

[vino yang]

+1 from my side

Best,
Vino

Terry Wang  于2019年6月12日周三 下午5:45写道：

> +1 for deprecation. It’s very reasonable.
>
> 在 2019年6月12日，下午5:32，Till Rohrmann  写道：
>
> +1 for deprecation.
>
> Cheers,
> Till
>
> On Wed, Jun 12, 2019 at 4:31 AM Hequn Cheng  wrote:
>
>> +1 on the proposal!
>> Maintaining only one Python API is helpful for users and contributors.
>>
>> Best, Hequn
>>
>> On Wed, Jun 12, 2019 at 9:41 AM Jark Wu  wrote:
>>
>>> +1 and looking forward to the new Python API world.
>>>
>>> Best,
>>> Jark
>>>
>>> On Wed, 12 Jun 2019 at 09:22, Becket Qin  wrote:
>>>
>>>> +1 on deprecating the old Python API in 1.9 release.
>>>>
>>>> Thanks,
>>>>
>>>> Jiangjie (Becket) Qin
>>>>
>>>> On Wed, Jun 12, 2019 at 9:07 AM Dian Fu  wrote:
>>>>
>>>>> +1 for this proposal.
>>>>>
>>>>> Regards,
>>>>> Dian
>>>>>
>>>>> 在 2019年6月12日，上午8:24，jincheng sun  写道：
>>>>>
>>>>> big +1 for the proposal.
>>>>>
>>>>> We will soon complete all the Python API functional development of the
>>>>> 1.9 release, the development of UDFs will be carried out. After the 
>>>>> support
>>>>> of UDFs is completed, it will be very natural to support Datastream API.
>>>>>
>>>>> If all of us agree with this proposal, I believe that for the 1.10
>>>>> release, it is possible to complete support both UDFs and DataStream API.
>>>>> And we will do our best to make the 1.10 release that contains the Python
>>>>> DataStream API support.
>>>>>
>>>>> So, great thanks to @Stephan for this proposal!
>>>>>
>>>>> Best,
>>>>> Jincheng
>>>>>
>>>>> Zili Chen  于2019年6月11日周二 下午10:56写道：
>>>>>
>>>>>> +1
>>>>>>
>>>>>> Best,
>>>>>> tison.
>>>>>>
>>>>>>
>>>>>> zhijiang  于2019年6月11日周二 下午10:52写道：
>>>>>>
>>>>>>> It is reasonable as stephan explained. +1 from my side!
>>>>>>>
>>>>>>> --
>>>>>>> From:Jeff Zhang 
>>>>>>> Send Time:2019年6月11日(星期二) 22:11
>>>>>>> To:Stephan Ewen 
>>>>>>> Cc:user ; dev 
>>>>>>> Subject:Re: [DISCUSS] Deprecate previous Python APIs
>>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> Stephan Ewen  于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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>

Re: [DISCUSS] Deprecate previous Python APIs

[Terry Wang]

+1 for deprecation. It’s very reasonable.

> 在 2019年6月12日，下午5:32，Till Rohrmann  写道：
> 
> +1 for deprecation.
> 
> Cheers,
> Till
> 
> On Wed, Jun 12, 2019 at 4:31 AM Hequn Cheng  <mailto:chenghe...@gmail.com>> wrote:
> +1 on the proposal!
> Maintaining only one Python API is helpful for users and contributors.
> 
> Best, Hequn
> 
> On Wed, Jun 12, 2019 at 9:41 AM Jark Wu  <mailto:imj...@gmail.com>> wrote:
> +1 and looking forward to the new Python API world.
> 
> Best,
> Jark
> 
> On Wed, 12 Jun 2019 at 09:22, Becket Qin  <mailto:becket@gmail.com>> wrote:
> +1 on deprecating the old Python API in 1.9 release.
> 
> Thanks,
> 
> Jiangjie (Becket) Qin
> 
> On Wed, Jun 12, 2019 at 9:07 AM Dian Fu  <mailto:dian0511...@gmail.com>> wrote:
> +1 for this proposal.
> 
> Regards,
> Dian
> 
>> 在 2019年6月12日，上午8:24，jincheng sun > <mailto:sunjincheng...@gmail.com>> 写道：
>> 
>> big +1 for the proposal.
>> 
>> We will soon complete all the Python API functional development of the 1.9 
>> release, the development of UDFs will be carried out. After the support of 
>> UDFs is completed, it will be very natural to support Datastream API. 
>> 
>> If all of us agree with this proposal, I believe that for the 1.10 release, 
>> it is possible to complete support both UDFs and DataStream API. And we will 
>> do our best to make the 1.10 release that contains the Python DataStream API 
>> support. 
>> 
>> So, great thanks to @Stephan for this proposal!
>> 
>> Best,
>> Jincheng
>> 
>> Zili Chen mailto:wander4...@gmail.com>> 于2019年6月11日周二 
>> 下午10:56写道：
>> +1
>> 
>> Best,
>> tison.
>> 
>> 
>> zhijiang mailto:wangzhijiang...@aliyun.com>> 
>> 于2019年6月11日周二 下午10:52写道：
>> It is reasonable as stephan explained. +1 from my side! 
>> --
>> From:Jeff Zhang mailto:zjf...@gmail.com>>
>> Send Time:2019年6月11日(星期二) 22:11
>> To:Stephan Ewen mailto:se...@apache.org>>
>> Cc:user mailto:user@flink.apache.org>>; dev 
>> mailto:d...@flink.apache.org>>
>> Subject:Re: [DISCUSS] Deprecate previous Python APIs
>>  
>> +1
>> 
>> Stephan Ewen mailto: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
>> 
> 

Re: [DISCUSS] Deprecate previous Python APIs

[Till Rohrmann]

+1 for deprecation.

Cheers,
Till

On Wed, Jun 12, 2019 at 4:31 AM Hequn Cheng  wrote:

> +1 on the proposal!
> Maintaining only one Python API is helpful for users and contributors.
>
> Best, Hequn
>
> On Wed, Jun 12, 2019 at 9:41 AM Jark Wu  wrote:
>
>> +1 and looking forward to the new Python API world.
>>
>> Best,
>> Jark
>>
>> On Wed, 12 Jun 2019 at 09:22, Becket Qin  wrote:
>>
>>> +1 on deprecating the old Python API in 1.9 release.
>>>
>>> Thanks,
>>>
>>> Jiangjie (Becket) Qin
>>>
>>> On Wed, Jun 12, 2019 at 9:07 AM Dian Fu  wrote:
>>>
>>>> +1 for this proposal.
>>>>
>>>> Regards,
>>>> Dian
>>>>
>>>> 在 2019年6月12日，上午8:24，jincheng sun  写道：
>>>>
>>>> big +1 for the proposal.
>>>>
>>>> We will soon complete all the Python API functional development of the
>>>> 1.9 release, the development of UDFs will be carried out. After the support
>>>> of UDFs is completed, it will be very natural to support Datastream API.
>>>>
>>>> If all of us agree with this proposal, I believe that for the 1.10
>>>> release, it is possible to complete support both UDFs and DataStream API.
>>>> And we will do our best to make the 1.10 release that contains the Python
>>>> DataStream API support.
>>>>
>>>> So, great thanks to @Stephan for this proposal!
>>>>
>>>> Best,
>>>> Jincheng
>>>>
>>>> Zili Chen  于2019年6月11日周二 下午10:56写道：
>>>>
>>>>> +1
>>>>>
>>>>> Best,
>>>>> tison.
>>>>>
>>>>>
>>>>> zhijiang  于2019年6月11日周二 下午10:52写道：
>>>>>
>>>>>> It is reasonable as stephan explained. +1 from my side!
>>>>>>
>>>>>> --
>>>>>> From:Jeff Zhang 
>>>>>> Send Time:2019年6月11日(星期二) 22:11
>>>>>> To:Stephan Ewen 
>>>>>> Cc:user ; dev 
>>>>>> Subject:Re: [DISCUSS] Deprecate previous Python APIs
>>>>>>
>>>>>> +1
>>>>>>
>>>>>> Stephan Ewen  于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
>>>>>>
>>>>>>
>>>>>>
>>>>

Re: [DISCUSS] Deprecate previous Python APIs

[Hequn Cheng]

+1 on the proposal!
Maintaining only one Python API is helpful for users and contributors.

Best, Hequn

On Wed, Jun 12, 2019 at 9:41 AM Jark Wu  wrote:

> +1 and looking forward to the new Python API world.
>
> Best,
> Jark
>
> On Wed, 12 Jun 2019 at 09:22, Becket Qin  wrote:
>
>> +1 on deprecating the old Python API in 1.9 release.
>>
>> Thanks,
>>
>> Jiangjie (Becket) Qin
>>
>> On Wed, Jun 12, 2019 at 9:07 AM Dian Fu  wrote:
>>
>>> +1 for this proposal.
>>>
>>> Regards,
>>> Dian
>>>
>>> 在 2019年6月12日，上午8:24，jincheng sun  写道：
>>>
>>> big +1 for the proposal.
>>>
>>> We will soon complete all the Python API functional development of the
>>> 1.9 release, the development of UDFs will be carried out. After the support
>>> of UDFs is completed, it will be very natural to support Datastream API.
>>>
>>> If all of us agree with this proposal, I believe that for the 1.10
>>> release, it is possible to complete support both UDFs and DataStream API.
>>> And we will do our best to make the 1.10 release that contains the Python
>>> DataStream API support.
>>>
>>> So, great thanks to @Stephan for this proposal!
>>>
>>> Best,
>>> Jincheng
>>>
>>> Zili Chen  于2019年6月11日周二 下午10:56写道：
>>>
>>>> +1
>>>>
>>>> Best,
>>>> tison.
>>>>
>>>>
>>>> zhijiang  于2019年6月11日周二 下午10:52写道：
>>>>
>>>>> It is reasonable as stephan explained. +1 from my side!
>>>>>
>>>>> --
>>>>> From:Jeff Zhang 
>>>>> Send Time:2019年6月11日(星期二) 22:11
>>>>> To:Stephan Ewen 
>>>>> Cc:user ; dev 
>>>>> Subject:Re: [DISCUSS] Deprecate previous Python APIs
>>>>>
>>>>> +1
>>>>>
>>>>> Stephan Ewen  于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
>>>>>
>>>>>
>>>>>
>>>

Re: [DISCUSS] Deprecate previous Python APIs

[Jark Wu]

+1 and looking forward to the new Python API world.

Best,
Jark

On Wed, 12 Jun 2019 at 09:22, Becket Qin  wrote:

> +1 on deprecating the old Python API in 1.9 release.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>
> On Wed, Jun 12, 2019 at 9:07 AM Dian Fu  wrote:
>
>> +1 for this proposal.
>>
>> Regards,
>> Dian
>>
>> 在 2019年6月12日，上午8:24，jincheng sun  写道：
>>
>> big +1 for the proposal.
>>
>> We will soon complete all the Python API functional development of the
>> 1.9 release, the development of UDFs will be carried out. After the support
>> of UDFs is completed, it will be very natural to support Datastream API.
>>
>> If all of us agree with this proposal, I believe that for the 1.10
>> release, it is possible to complete support both UDFs and DataStream API.
>> And we will do our best to make the 1.10 release that contains the Python
>> DataStream API support.
>>
>> So, great thanks to @Stephan for this proposal!
>>
>> Best,
>> Jincheng
>>
>> Zili Chen  于2019年6月11日周二 下午10:56写道：
>>
>>> +1
>>>
>>> Best,
>>> tison.
>>>
>>>
>>> zhijiang  于2019年6月11日周二 下午10:52写道：
>>>
>>>> It is reasonable as stephan explained. +1 from my side!
>>>>
>>>> --
>>>> From:Jeff Zhang 
>>>> Send Time:2019年6月11日(星期二) 22:11
>>>> To:Stephan Ewen 
>>>> Cc:user ; dev 
>>>> Subject:Re: [DISCUSS] Deprecate previous Python APIs
>>>>
>>>> +1
>>>>
>>>> Stephan Ewen  于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
>>>>
>>>>
>>>>
>>

Re: [DISCUSS] Deprecate previous Python APIs

[Becket Qin]

+1 on deprecating the old Python API in 1.9 release.

Thanks,

Jiangjie (Becket) Qin

On Wed, Jun 12, 2019 at 9:07 AM Dian Fu  wrote:

> +1 for this proposal.
>
> Regards,
> Dian
>
> 在 2019年6月12日，上午8:24，jincheng sun  写道：
>
> big +1 for the proposal.
>
> We will soon complete all the Python API functional development of the 1.9
> release, the development of UDFs will be carried out. After the support of
> UDFs is completed, it will be very natural to support Datastream API.
>
> If all of us agree with this proposal, I believe that for the 1.10
> release, it is possible to complete support both UDFs and DataStream API.
> And we will do our best to make the 1.10 release that contains the Python
> DataStream API support.
>
> So, great thanks to @Stephan for this proposal!
>
> Best,
> Jincheng
>
> Zili Chen  于2019年6月11日周二 下午10:56写道：
>
>> +1
>>
>> Best,
>> tison.
>>
>>
>> zhijiang  于2019年6月11日周二 下午10:52写道：
>>
>>> It is reasonable as stephan explained. +1 from my side!
>>>
>>> --------------
>>> From:Jeff Zhang 
>>> Send Time:2019年6月11日(星期二) 22:11
>>> To:Stephan Ewen 
>>> Cc:user ; dev 
>>> Subject:Re: [DISCUSS] Deprecate previous Python APIs
>>>
>>> +1
>>>
>>> Stephan Ewen  于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
>>>
>>>
>>>
>

Re: [DISCUSS] Deprecate previous Python APIs

[Dian Fu]

+1 for this proposal.

Regards,
Dian

> 在 2019年6月12日，上午8:24，jincheng sun  写道：
> 
> big +1 for the proposal.
> 
> We will soon complete all the Python API functional development of the 1.9 
> release, the development of UDFs will be carried out. After the support of 
> UDFs is completed, it will be very natural to support Datastream API. 
> 
> If all of us agree with this proposal, I believe that for the 1.10 release, 
> it is possible to complete support both UDFs and DataStream API. And we will 
> do our best to make the 1.10 release that contains the Python DataStream API 
> support. 
> 
> So, great thanks to @Stephan for this proposal!
> 
> Best,
> Jincheng
> 
> Zili Chen mailto:wander4...@gmail.com>> 于2019年6月11日周二 
> 下午10:56写道：
> +1
> 
> Best,
> tison.
> 
> 
> zhijiang mailto:wangzhijiang...@aliyun.com>> 
> 于2019年6月11日周二 下午10:52写道：
> It is reasonable as stephan explained. +1 from my side! 
> --
> From:Jeff Zhang mailto:zjf...@gmail.com>>
> Send Time:2019年6月11日(星期二) 22:11
> To:Stephan Ewen mailto:se...@apache.org>>
> Cc:user mailto:user@flink.apache.org>>; dev 
> mailto:d...@flink.apache.org>>
> Subject:Re: [DISCUSS] Deprecate previous Python APIs
>  
> +1
> 
> Stephan Ewen mailto: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
> 

Re: [DISCUSS] Deprecate previous Python APIs

[jincheng sun]

big +1 for the proposal.

We will soon complete all the Python API functional development of the 1.9
release, the development of UDFs will be carried out. After the support of
UDFs is completed, it will be very natural to support Datastream API.

If all of us agree with this proposal, I believe that for the 1.10 release,
it is possible to complete support both UDFs and DataStream API. And we
will do our best to make the 1.10 release that contains the Python
DataStream API support.

So, great thanks to @Stephan for this proposal!

Best,
Jincheng

Zili Chen  于2019年6月11日周二 下午10:56写道：

> +1
>
> Best,
> tison.
>
>
> zhijiang  于2019年6月11日周二 下午10:52写道：
>
>> It is reasonable as stephan explained. +1 from my side!
>>
>> --
>> From:Jeff Zhang 
>> Send Time:2019年6月11日(星期二) 22:11
>> To:Stephan Ewen 
>> Cc:user ; dev 
>> Subject:Re: [DISCUSS] Deprecate previous Python APIs
>>
>> +1
>>
>> Stephan Ewen  于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
>>
>>
>>

Re: [DISCUSS] Deprecate previous Python APIs

[Zili Chen]

+1

Best,
tison.


zhijiang  于2019年6月11日周二 下午10:52写道：

> It is reasonable as stephan explained. +1 from my side!
>
> --
> From:Jeff Zhang 
> Send Time:2019年6月11日(星期二) 22:11
> To:Stephan Ewen 
> Cc:user ; dev 
> Subject:Re: [DISCUSS] Deprecate previous Python APIs
>
> +1
>
> Stephan Ewen  于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
>
>
>

Re: [DISCUSS] Deprecate previous Python APIs

[zhijiang]

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

Stephan Ewen  于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

Re: [DISCUSS] Deprecate previous Python APIs

[Jeff Zhang]

+1

Stephan Ewen  于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

[DISCUSS] Deprecate previous Python APIs

[Stephan Ewen]

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