Re: [DISCUSS] Feature freeze for Flink 1.7

2018-10-02 Thread Till Rohrmann
Thanks for the feedback. For FLINK-10122, the proper solution would require the redesigned source interface which will most likely not make it into the release. I think the community is working hard on implementing it as fast as possible, though. Concerning state migration, Gordon is the best to

Re: [DISCUSS] Feature freeze for Flink 1.7

2018-10-01 Thread David Anderson
What would this timing mean for the epic around state schema evolution and state migration? On Mon, Oct 1, 2018 at 10:43 AM Piotr Nowojski wrote: > Hi, > > I think that’s a good time for the release, will give us some time before > holidays season for potential bug fixes. > > Piotrek > > > On 29

Re: [DISCUSS] Feature freeze for Flink 1.7

2018-10-01 Thread Piotr Nowojski
Hi, I think that’s a good time for the release, will give us some time before holidays season for potential bug fixes. Piotrek > On 29 Sep 2018, at 05:08, Steven Wu wrote: > > Please prioritize a proper long-term fix for this issue. it is a big > scalability issue for high-parallelism job (e.

Re: [DISCUSS] Feature freeze for Flink 1.7

2018-09-28 Thread Steven Wu
Please prioritize a proper long-term fix for this issue. it is a big scalability issue for high-parallelism job (e.g. over 1,000). FLINK-10122 KafkaConsumer should use partitionable state over union state if partition discovery is not active On Fri, Sep 28, 2018 at 7:20 AM Till Rohrmann wrote:

[DISCUSS] Feature freeze for Flink 1.7

2018-09-28 Thread Till Rohrmann
Dear community, almost 2 months have passed since the Flink 1.6 release and some good features for the next major release are close to completion. Therefore, I would like to discuss a possible feature freeze for Flink 1.7. Given that we've released Flink 1.6 at the beginning of August, I would li