Re: [DISCUSS] Planning Flink 1.12

@David Anderson I think we can get that into 1.12. I have a branch that just needs to be cleaned up. +1 for https://issues.apache.org/jira/browse/FLINK-13095 On Mon, Aug 17, 2020 at 2:03 AM Till Rohrmann wrote: > Hi Rodrigo, > > FLINK-10407 has not been up to date with the actual progress on t

Re: [DISCUSS] Planning Flink 1.12

Hi Rodrigo, FLINK-10407 has not been up to date with the actual progress on the feature. We will update it soon. I think that the community won't actively work on FLINK-12002 in this release. However, we will work on FLINK-16430 [1] and once this is done continue with the clean up of the legacy s

Re: [DISCUSS] Planning Flink 1.12

Thanks Dian! About the wiki page, I think that the "Reactive-scaling mode" by Till has an open issue on FLINK-10407 [1]. Still about scaling, what about the adaptive parallelism of jobs [2]? This is somehow related to Prasanna and Harold's comments above. It seems to depend on finishing the old

Re: [DISCUSS] Planning Flink 1.12

What about filling in at least the most critical holes in the State Processor API? As it stands now, many of its supposed benefits (e.g., migrate between state backends, change max parallelism) can't be realized for applications that use windows. https://issues.apache.org/jira/browse/FLINK-13095 -

Re: [DISCUSS] Planning Flink 1.12

What about the work of migrating some Flink sources to the new FLIP-27 source interface? They are not listed in the 1.12 release wiki page. On Thu, Aug 13, 2020 at 6:51 PM Dian Fu wrote: > Hi Rodrigo, > > Both FLIP-130 and FLIP-133 will be in the list of 1.12. Besides, there are > also some othe

Re: [DISCUSS] Planning Flink 1.12

Hi Rodrigo, Both FLIP-130 and FLIP-133 will be in the list of 1.12. Besides, there are also some other features from PyFlink side in 1.12. More details could be found in the wiki page(https://cwiki.apache.org/confluence/display/FLINK/1.12+Release

Re: [DISCUSS] Planning Flink 1.12

Hi, I hope it's not too late to ask, but would FLIP-130 [1] and FLIP-133 [2] be considered? I think that it would be nice to have some details of pyFlink Datastreams API (FLIP-130) on the roadmap, giving us (users) more insights into what we can expect from pyFlink in the near future. [1] http:/

Re: [DISCUSS] Planning Flink 1.12

I updated the release date in the Wiki page. On Sun, Aug 9, 2020 at 8:18 PM Yun Tang wrote: > +1 for extending the feature freeze due date. > > From: Zhijiang > Sent: Thursday, August 6, 2020 17:05 > To: dev > Subject: Re: [DISCUSS] Planning

Re: [DISCUSS] Planning Flink 1.12

+1 for extending the feature freeze due date. From: Zhijiang Sent: Thursday, August 6, 2020 17:05 To: dev Subject: Re: [DISCUSS] Planning Flink 1.12 +1 on my side for feature freeze date by the end of Oct

Re: [DISCUSS] Planning Flink 1.12

+1 on my side for feature freeze date by the end of Oct. -- From:Yuan Mei Send Time:2020年8月6日(星期四) 14:54 To:dev Subject:Re: [DISCUSS] Planning Flink 1.12 +1 > +1 for extending the feature freeze date to the end of October.

Re: [DISCUSS] Planning Flink 1.12

+1 > +1 for extending the feature freeze date to the end of October. On Thu, Aug 6, 2020 at 12:08 PM Yu Li wrote: > +1 for extending feature freeze date to end of October. > > Feature development in the master branch could be unblocked through > creating the release branch, but every coin has

Re: [DISCUSS] Planning Flink 1.12

+1 for extending feature freeze date to end of October. Feature development in the master branch could be unblocked through creating the release branch, but every coin has its two sides (smile) Best Regards, Yu On Wed, 5 Aug 2020 at 20:12, Robert Metzger wrote: > Thanks all for your opinion.

Re: [DISCUSS] Planning Flink 1.12

Thanks all for your opinion. @Chesnay: That is a risk, but I hope the people responsible for individual FLIPs plan accordingly. Extending the time till the feature freeze should not mean that we are extending the scope of the release. Ideally, features are done before FF, and they use the time til

Re: [DISCUSS] Planning Flink 1.12

I'm a bit concerned about end of October, because it means we have Flink forward, which usually means at least 1 week of little-to-no activity, and then 1 week until feature-freeze. On 05/08/2020 11:56, jincheng sun wrote: +1 for end of October from me as well. Best, Jincheng Kostas Kloudas

Re: [DISCUSS] Planning Flink 1.12

+1 for end of October from me as well. Best, Jincheng Kostas Kloudas 于2020年8月5日周三 下午4:59写道： > +1 for end of October from me as well. > > Cheers, > Kostas > > On Wed, Aug 5, 2020 at 9:59 AM Till Rohrmann wrote: > > > +1 for end of October from my side as well. > > > > Cheers, > > Till > > > >

Re: [DISCUSS] Planning Flink 1.12

+1 for end of October from me as well. Cheers, Kostas On Wed, Aug 5, 2020 at 9:59 AM Till Rohrmann wrote: > +1 for end of October from my side as well. > > Cheers, > Till > > On Tue, Aug 4, 2020 at 9:46 PM Stephan Ewen wrote: > > > The end of October sounds good from my side, unless it collide

Re: [DISCUSS] Planning Flink 1.12

+1 for end of October from my side as well. Cheers, Till On Tue, Aug 4, 2020 at 9:46 PM Stephan Ewen wrote: > The end of October sounds good from my side, unless it collides with some > holidays that affect many committers. > > Feature-wise, I believe we can definitely make good use of the time

Re: [DISCUSS] Planning Flink 1.12

The end of October sounds good from my side, unless it collides with some holidays that affect many committers. Feature-wise, I believe we can definitely make good use of the time to wrap up some critical threads (like finishing the FLIP-27 source efforts). So +1 to the end of October from my sid

Re: [DISCUSS] Planning Flink 1.12

Thanks a lot for commenting on the feature freeze date. You are raising a few good points on the timing. If we have already (2 months before) concerns regarding the deadline, then I agree that we should move it till the end of October. We then just need to be careful not to run into the Christmas

Re: [DISCUSS] Planning Flink 1.12

Regarding setting the feature freeze date to late September, I have some concern that it might make the development time of 1.12 too short. One reason for this is we took too much time (about 1.5 month, from mid of May to beginning of July) for testing 1.11. It's not ideal but further squeeze the

Re: [DISCUSS] Planning Flink 1.12

Hi all, Thanks a lot for the responses so far. I've put them into this Wiki page: https://cwiki.apache.org/confluence/display/FLINK/1.12+Release to keep track of them. Ideally, post JIRA tickets for your feature, then the status will update automatically in the wiki :) Please keep posting feature

Re: [DISCUSS] Planning Flink 1.12

Thanks for being our release managers for the 1.12 release Dian & Robert! Here are some features I would like to work on for this release: # Features ## Finishing pipelined region scheduling ( https://issues.apache.org/jira/browse/FLINK-16430) With the pipelined region scheduler we want to imple

Re: [DISCUSS] Planning Flink 1.12

Hi All, Thanks for bring-up this discussion, Robert! Congratulations on becoming the release manager of 1.12， Dian and Robert ! -- Here are some of my thoughts of the features for native integration with Kubernetes in Flink 1.12: 1. Support user-specified pod templates Description:

Re: [DISCUSS] Planning Flink 1.12

I'm excited to hear about this feature, very, very, very highly encouraged Prasanna kumar 于2020年7月23日周四 上午12:10写道： > Hi Flink Dev Team, > > Dynamic AutoScaling Based on the incoming data load would be a great > feature. > > We should be able have some rule say If the load increased by 20% , ad

Re: [DISCUSS] Planning Flink 1.12

Hi All, Thanks for bring-up this discussion, Robert! Congratulations on becoming the release manager of 1.12， Dian and Robert ! -- Here is my thoughts of the features for PyFlink in Flink 1.12: 1. Improve the usabilities for PyFlink Description: Improve the usabilities for PyFlin

Re: [DISCUSS] Planning Flink 1.12

Thanks Robert for bringing up this discussion. This is very important to ensure that we have a smooth release process as there are only two months left before feature freeze. It would be good to have a list of the features for 1.12 as soon as possible. Welcome any one to post the feature list w

Re: [DISCUSS] Planning Flink 1.12

Hi Flink Dev Team, Dynamic AutoScaling Based on the incoming data load would be a great feature. We should be able have some rule say If the load increased by 20% , add extra resource should be added. Or time based say during these peak hours the pipeline should scale automatically by 50%. This

[DISCUSS] Planning Flink 1.12

Hi all, Now that the 1.11 release is out, it is time to plan for the next major Flink release. Some items: 1. Dian Fu and me volunteer to be the release managers for Flink 1.12. 1. Timeline: We propose to stick to our approximate 4 month release cycle, thus the release should