Hi Chesnay,

Here is the JIRA list I have collected, all of them are under reviewing:

1. Hive UDF support (FLINK-13024, FLINK-13225)
2. Partition prune support (FLINK-13115)
3. Set StreamGraph properties in blink planner (FLINK-13121)
4. Support HBase upsert sink (FLINK-10245)
5. Support JDBC TableFactory (FLINK-13118)
6. Fix the bug of throwing IOException while FileBufferReader#nextBuffer
(FLINK-13110)
7. Bookkeeping of available resources of allocated slots in SlotPool
(FLINK-12765)
8. Introduce ScheduleMode#LAZY_FROM_SOURCES_WITH_BATCH_SLOT_REQUEST
(FLINK-13187)
9. Add support for batch slot requests to SlotPoolImpl (FLINK-13166)
10. Complete slot requests in request order (FLINK-13165)

Best,
Kurt


On Thu, Jul 11, 2019 at 6:12 PM Chesnay Schepler <ches...@apache.org> wrote:

> Can we get JIRA's attached to these items so people out of the loop can
> track the progress?
>
> On 05/07/2019 16:06, Kurt Young wrote:
> > Here are the features I collected which are under actively developing and
> > close
> > to merge:
> >
> > 1. Bridge blink planner to unified table environment and remove
> TableConfig
> > from blink planner
> > 2. Support timestamp with local time zone and partition pruning in blink
> > planner
> > 3. Support JDBC & HBase lookup function and upsert sink
> > 4. StreamExecutionEnvironment supports executing job with StreamGraph,
> and
> > blink planner should set proper properties to StreamGraph
> > 5. Set resource profiles to task and enable managed memory as resource
> > profile
> >
> > Best,
> > Kurt
> >
> >
> > On Fri, Jul 5, 2019 at 9:37 PM Kurt Young <ykt...@gmail.com> wrote:
> >
> >> Hi devs,
> >>
> >> It's July 5 now and we should announce feature freeze and cut the branch
> >> as planned. However, some components seems still not ready yet and
> >> various features are still under development or review.
> >>
> >> But we also can not extend the freeze day again which will further delay
> >> the
> >> release date. I think freeze new features today and have another couple
> >> of buffer days, letting features which are almost ready have a chance to
> >> get in is a reasonable solution.
> >>
> >> I hereby announce features of Flink 1.9.0 are freezed, *July 11* will be
> >> the
> >> day for cutting branch.  Since the feature freeze has effectively took
> >> place,
> >> I kindly ask committers to refrain from merging features that are
> planned
> >> for
> >> future releases into the master branch for the time being before the 1.9
> >> branch
> >> is cut. We understand this might be a bit inconvenient, thanks for the
> >> cooperation here.
> >>
> >> Best,
> >> Kurt
> >>
> >>
> >> On Fri, Jul 5, 2019 at 5:19 PM 罗齐 <luoqi...@bytedance.com> wrote:
> >>
> >>> Hi Gordon,
> >>>
> >>> Will branch 1.9 be cut out today? We're really looking forward to the
> >>> blink features in 1.9.
> >>>
> >>> Thanks,
> >>> Qi
> >>>
> >>> On Wed, Jun 26, 2019 at 7:18 PM Tzu-Li (Gordon) Tai <
> tzuli...@apache.org>
> >>> wrote:
> >>>
> >>>> Thanks for the updates so far everyone!
> >>>>
> >>>> Since support for the new Blink-based Table / SQL runner and
> fine-grained
> >>>> recovery are quite prominent features for 1.9.0,
> >>>> and developers involved in these topics have already expressed that
> these
> >>>> could make good use for another week,
> >>>> I think it definitely makes sense to postpone the feature freeze.
> >>>>
> >>>> The new date for feature freeze and feature branch cut for 1.9.0 will
> be
> >>>> *July
> >>>> 5*.
> >>>>
> >>>> Please update on this thread if there are any further concerns!
> >>>>
> >>>> Cheers,
> >>>> Gordon
> >>>>
> >>>> On Tue, Jun 25, 2019 at 9:05 PM Chesnay Schepler <ches...@apache.org>
> >>>> wrote:
> >>>>
> >>>>> On the fine-grained recovery / batch scheduling side we could make
> good
> >>>>> use of another week.
> >>>>> Currently we are on track to have the _feature_ merged, but without
> >>>>> having done a great deal of end-to-end testing.
> >>>>>
> >>>>> On 25/06/2019 15:01, Kurt Young wrote:
> >>>>>> Hi Aljoscha,
> >>>>>>
> >>>>>> I also feel an additional week can make the remaining work more
> >>>> easy. At
> >>>>>> least
> >>>>>> we don't have to check in lots of commits in both branches (master &
> >>>>>> release-1.9).
> >>>>>>
> >>>>>> Best,
> >>>>>> Kurt
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Jun 25, 2019 at 8:27 PM Aljoscha Krettek <
> >>>> aljos...@apache.org>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> A few threads are converging around supporting the new Blink-based
> >>>> Table
> >>>>>>> API Runner/Planner. I think hitting the currently proposed feature
> >>>>> freeze
> >>>>>>> date is hard, if not impossible, and that the work would benefit
> >>>> from an
> >>>>>>> additional week to get everything in with good quality.
> >>>>>>>
> >>>>>>> What do the others involved in the topic think?
> >>>>>>>
> >>>>>>> Aljoscha
> >>>>>>>
> >>>>>>>> On 24. Jun 2019, at 19:42, Bowen Li <bowenl...@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Hi Gordon,
> >>>>>>>>
> >>>>>>>> Thanks for driving this effort.
> >>>>>>>>
> >>>>>>>> Xuefu responded to the discussion thread [1] and I want to bring
> >>>> that
> >>>>> to
> >>>>>>>> our attention here:
> >>>>>>>>
> >>>>>>>> Hive integration depends on a few features that are actively
> >>>> developed.
> >>>>>>> If
> >>>>>>>> the completion of those features don't leave enough time for us to
> >>>>>>>> integrate, then our work can potentially go beyond the proposed
> >>>> date.
> >>>>>>>> Just wanted to point out such a dependency adds uncertainty.
> >>>>>>>>
> >>>>>>>> [1]
> >>>>>>>>
> >>>>
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Features-for-Apache-Flink-1-9-0-td28701.html
> >>>>>>>> On Thu, Jun 20, 2019 at 1:05 AM Tzu-Li (Gordon) Tai <
> >>>>> tzuli...@apache.org
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Hi devs,
> >>>>>>>>>
> >>>>>>>>> Per the feature discussions for 1.9.0 [1], I hereby announce the
> >>>>>>> official
> >>>>>>>>> feature freeze for Flink 1.9.0 to be on June 28. A release
> feature
> >>>>>>> branch
> >>>>>>>>> for 1.9 will be cut following that date.
> >>>>>>>>>
> >>>>>>>>> We’re roughly one week away from this date, but please keep in
> >>>> mind
> >>>>>>> that we
> >>>>>>>>> still shouldn’t rush things. If you feel that there may be
> >>>> problems
> >>>>> with
> >>>>>>>>> this schedule for the things you are working on, please let us
> >>>> know
> >>>>>>> here.
> >>>>>>>>> Cheers,
> >>>>>>>>> Gordon
> >>>>>>>>>
> >>>>>>>>> [1]
> >>>>>>>>>
> >>>>>>>>>
> >>>>
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Features-for-Apache-Flink-1-9-0-td28701.html
> >>>>>
>
>

Reply via email to