Any chance to cherry-pick this also into 1.2.1? We're usign Flink 1.2.0 in production and maybe an upgrade to 1.2.1 would be a safer option in the short term..
Best, Flavio On Fri, Apr 28, 2017 at 2:00 PM, Aljoscha Krettek <aljos...@apache.org> wrote: > Ah, I see. The fix for that has been merged into master so it will be > release in Flink 1.3. > > > On 28. Apr 2017, at 13:50, Flavio Pompermaier <pomperma...@okkam.it> > wrote: > > > > Sorry, you're right Aljosha..the issue number is correct, the link is > > wrong! The correct one is https://issues.apache.org/ > jira/browse/FLINK-6398 > > > > On Fri, Apr 28, 2017 at 11:48 AM, Aljoscha Krettek <aljos...@apache.org> > > wrote: > > > >> I think there might be a typo. We haven’t yet reached issue number 6389, > >> if I’m not mistaken. The latest as I’m writing this is 6410. > >> > >>> On 28. Apr 2017, at 10:00, Flavio Pompermaier <pomperma...@okkam.it> > >> wrote: > >>> > >>> If it's not a problem it will be great for us to include also > FLINK-6398 > >>> <https://issues.apache.org/jira/browse/FLINK-6938> if it's not a big > >> deal > >>> > >>> Best, > >>> Flavio > >>> > >>> On Fri, Apr 28, 2017 at 3:32 AM, Zhuoluo Yang < > >> zhuoluo....@alibaba-inc.com> > >>> wrote: > >>> > >>>> Hi Devs, > >>>> > >>>> Thanks for the release plan. > >>>> > >>>> Could you also please add the feature FLINK-6196 > >>>> <https://issues.apache.org/jira/browse/FLINK-6196> Support dynamic > >> schema > >>>> in Table Function? > >>>> I’d like to update the code as comments left on PR today. > >>>> I will try to make sure the code is updated before the Apr 30th. > >>>> > >>>> > >>>> Thanks, > >>>> > >>>> Zhuoluo 😀 > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> 在 2017年4月28日，上午8:48，Haohui Mai <ricet...@gmail.com> 写道： > >>>> > >>>> Hello, > >>>> > >>>> Thanks for starting this thread. It would be great to see the > following > >>>> features available in Flink 1.3: > >>>> > >>>> * Support for complex schema: FLINK-6033, FLINK-6377 > >>>> * Various improvements on SQL over group windows: FLINK-6335, > FLINK-6373 > >>>> * StreamTableSink for JDBC and Cassandra: FLINK-6281, FLINK-6225 > >>>> * Decoupling Flink and Hadoop: FLINK-5998 > >>>> > >>>> All of them have gone through at least one round of review so I'm > >>>> optimistic that they can make it to 1.3 in a day or two. > >>>> > >>>> Additionally it would be great to see FLINK-6232 go in, but it depends > >> on > >>>> FLINK-5884 so it might be a little bit tough. > >>>> > >>>> Regards, > >>>> Haohui > >>>> > >>>> On Thu, Apr 27, 2017 at 12:22 PM Chesnay Schepler <ches...@apache.org > > > >>>> wrote: > >>>> > >>>> Hello, > >>>> > >>>> FLINK-5892 (Restoring state by operator) is also nearing completion, > but > >>>> with only 1 day left before the weekend we're cutting it really short. > >>>> > >>>> Since this eliminates a major pain point when updating jobs, as it > >>>> allows the modification of chains, another day or 2 would be good i > >> think. > >>>> > >>>> Regards, > >>>> Chesnay > >>>> > >>>> On 27.04.2017 18:55, Bowen Li wrote: > >>>> > >>>> Hi Ufuk, > >>>> I'd like to get FLINK-6013 (Adding Datadog Http metrics reporter) > >>>> > >>>> into > >>>> > >>>> release 1.3. It's in the final state of code review in > >>>> https://github.com/apache/flink/pull/3736 > >>>> > >>>> Thanks, > >>>> Bowen > >>>> > >>>> On Thu, Apr 27, 2017 at 8:38 AM, Zhijiang(wangzhijiang999) < > >>>> wangzhijiang...@aliyun.com> wrote: > >>>> > >>>> Hi Ufuk, > >>>> Thank you for launching this topic! > >>>> I wish my latest refinement of buffer provider ( > >>>> > >>>> https://issues.apache.org/ > >>>> > >>>> jira/browse/FLINK-6337) to be included in 1.3 and most of the jobs > can > >>>> get benefit from it. And I think it can be completed with the help of > >>>> > >>>> your > >>>> > >>>> reviews this week. > >>>> > >>>> Cheers,Zhijiang--------------------------------------------- > >>>> ---------------------发件人：Ufuk > >>>> > >>>> Celebi <u...@apache.org>发送时间：2017年4月27日(星期四) 22:25收件人：dev < > >>>> dev@flink.apache.org>抄 送：Robert Metzger <rmetz...@apache.org>主 > >>>> 题：[DISCUSS] Feature Freeze > >>>> Hey devs! :-) > >>>> > >>>> We decided to follow a time-based release model with the upcoming 1.3 > >>>> release and the planned feature freeze is on Monday, May 1st. > >>>> > >>>> I wanted to start a discussion to get a quick overview of the current > >>>> state of things. > >>>> > >>>> - Is everyone on track and aware of the feature freeze? ;) > >>>> - Are there any major features we want in 1.3 that > >>>> have not been merged yet? > >>>> - Do we need to extend the feature freeze, because of an > >>>> important feature? > >>>> > >>>> Would be great to gather a list of features/PRs that we want in the > >>>> 1.3 release. This could be a good starting point for the release > >>>> manager (@Robert?). > >>>> > >>>> Best, > >>>> > >>>> Ufuk > >>>> > >>>> > >>>> > >>>> > >>>> > >> > >> >
