Hi Jincheng, Yes, your help would be very helpful. Thanks a lot!
Best Regards, Yu On Tue, 10 Mar 2020 at 18:24, jincheng sun <sunjincheng...@gmail.com> wrote: > Thanks for bring up the discussion Yu. I would like to give you a hand at > the last stage when the RC is finished.(If you need) :) > > Best, > Jincheng > > > > Yu Li <car...@gmail.com> 于2020年3月10日周二 下午5:49写道： > > > Hi All, > > > > It has been almost one month since we released Flink 1.10.0. We already > > have more than 40 resolved improvements/bugs in the release-1.10 branch, > > and I propose to start the 1.10.1 release cycle. > > > > Most noticeable fixes are: > > > > - FLINK-16241 [legal] Remove the license and notice file in flink-ml-lib > > module > > - FLINK-16313 Fix RocksDB resource leak in flink-state-processor-api > > - FLINK-16161 Statistics zero should be known in HiveCatalog > > - FLINK-2336 ArrayIndexOufOBoundsException in TypeExtractor when mapping > > - FLINK-16108 StreamSQLExample is failed if running in blink planner > > - FLINK-16139 Co-location constraints are not reset on task recovery in > > DefaultScheduler > > - FLINK-16414 Create udaf/udtf function using sql casuing > > ValidationException: SQL validation failed > > > > Furthermore, I think the following issues should be merged before 1.10.1 > > release (especially the Metaspace OOM issue): > > > > - FLINK-16142 Memory Leak causes Metaspace OOM error on repeated job > > submission > > - FLINK-16406 Increase default value for JVM Metaspace to minimise its > > OutOfMemoryError > > - FLINK-16047 Blink planner produces wrong aggregate results with state > > clean up > > - FLINK-16070 Blink planner can not extract correct unique key for > > UpsertStreamTableSink > > > > I would volunteer as the release manager and kick off the release process > > once blocker issues are merged. What do you think? > > > > If there are any concerns or missing blocker issues need to be fixed in > > 1.10.1, please let me know. Thanks. > > > > Best Regards, > > Yu > > >
