flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fabian Hueske <fhue...@gmail.com>
Subject Re: [DISCUSS] Feature Freeze
Date Thu, 27 Apr 2017 14:58:10 GMT
Hi everybody,

from an Table API / SQL point of view, three major features are not
completed yet:
- user-defined aggregation functions: Most of the preparation work is done.
There is one PR missing to actually register and analyze UDAGGs.
- retraction support: This feature was developed in a feature branch
(table-retraction) and is almost complete as well. There is one PR missing
for the conversion of Tables to DataStreams.
- time indicators: Timo is working on this feature and AFAIK, close to
finish it.

I know that the contributors for the UDAGG and retraction support are
working on their last PRs right now.

So, from the Table API / SQL point of view, we are very! close to finish
our efforts.
A few days more time before the feature freeze would help to ensure that
the Table API / SQL makes a huge step forward with Flink 1.3.

Cheers, Fabian


2017-04-27 16:44 GMT+02:00 Henry Saputra <henry.saputra@gmail.com>:

> The FLINK-6364 <https://issues.apache.org/jira/browse/FLINK-6364> seems
> need an accompanying FLIP [1] to help review.
>
> I dont see for this one in the list of existing proposals.
>
> - Henry
>
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/
> Flink+Improvement+Proposals
>
> On Thu, Apr 27, 2017 at 7:39 AM, Gyula Fóra <gyula.fora@gmail.com> wrote:
>
> > Hi Ufuk,
> >
> > Thanks for starting this discussion!
> >
> > One feature that immediately comes to my mind is incremental
> checkpointing
> > given it's production impact.
> >
> > https://issues.apache.org/jira/browse/FLINK-6364
> >
> > It would be good to get some better understanding how the implementation
> > effort is going and whether it is reasonable to expect this to be
> included
> > in 1.3.
> >
> > Regards,
> > Gyula
> >
> > Ufuk Celebi <uce@apache.org> ezt írta (időpont: 2017. ápr. 27., Cs,
> > 16:24):
> >
> > > 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
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message