flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Flavio Pompermaier <pomperma...@okkam.it>
Subject Re: [DISCUSS] Schedule and Scope for Flink 1.2
Date Mon, 21 Nov 2016 14:03:52 GMT
Hi to all,
we've completed the PR #2790 <https://github.com/apache/flink/pull/2790> to
implement FLINK-4491 <https://issues.apache.org/jira/browse/FLINK-4491>:
we've added the comment that @zentol asked for a week ago and we also fixed
a potential annoying problem we faced during indexing (if a malformed
document generates an error during indexing, the close() method throws an
exception forcing the entire job to fail, killing other threads that are
still indexing). I hope this PR could hep other people working with
Elasticsearch, right from the next release ;)

On Mon, Nov 14, 2016 at 2:47 PM, Flavio Pompermaier <pompermaier@okkam.it>
wrote:

> Hi to all,
> for the 1.2 release do you think it will be possible to include also a PR
> to implement FLINK-4491 <https://issues.apache.org/jira/browse/FLINK-4491>
> ?
> The PR is waiting for a review at https://github.com/apache/
> flink/pull/2790.
>
> Best,
> Flavio
>
> On Fri, Oct 28, 2016 at 5:59 PM, Fabian Hueske <fhueske@gmail.com> wrote:
>
>> Hi Jark,
>>
>> FLINK-4469: I agree, UDTFs would be a great feature. I don't think we
>> should make it a blocker but I will help to get it the master before the
>> feature freeze.
>> FLINK-4704: Regarding the renaming of the namespace, we have two positive
>> votes in JIRA, but we should also start a discussion on the dev and user
>> list to collect some more input. The actual change should be simple.
>>
>> @Everybody: I created a wiki page for the 1.2 release [1] and added all
>> features discussed in this thread so far.
>> Please have a look at the page and update it if you know the JIRAs and/or
>> state of the features.
>>
>> Cheers, Fabian
>>
>> [1] https://cwiki.apache.org/confluence/display/FLINK/1.2+Release
>>
>> 2016-10-28 15:28 GMT+02:00 Kostas Kloudas <k.kloudas@data-artisans.com>:
>>
>> > Hello,
>> >
>> > As Aljoshca said, the TriggerDSL depends on another PR, before it can be
>> > merged.
>> > In addition, this will change also the whole structure of how we test
>> > window/trigger
>> > related functionality, so some refactoring will be required.
>> >
>> > Kostas
>> >
>> > > On Oct 28, 2016, at 3:06 PM, Aljoscha Krettek <aljoscha@apache.org>
>> > wrote:
>> > >
>> > > @Till: For the TriggerDSL we have to merge my open PR [1] for
>> refactoring
>> > > the WindowOperator/Trigger tests and then refactor the tests of the
>> > > TriggerDSL to use the new test facilities introduced there. Plus then
>> > maybe
>> > > some fixups.
>> > >
>> > > On Fri, 28 Oct 2016 at 11:17 Jark Wu <wuchong.wc@alibaba-inc.com>
>> wrote:
>> > >
>> > >> +1 to the schedule
>> > >>
>> > >> I hope to add
>> > >>
>> > >> 1) Table API: User defined table function (FLINK-4469 <
>> > >> https://issues.apache.org/jira/browse/FLINK-4469>)
>> > >> 2) Table API: Move Table API to org.apache.flink.table (FLINK-4704
<
>> > >> https://issues.apache.org/jira/browse/FLINK-4704>)
>> > >>
>> > >> The 1) has been discussed for a long time and a pull request has
>> been on
>> > >> github. The 2) would be a large change, but I hope it could be
>> included
>> > in
>> > >> 1.2 release, otherwise it will be more difficult to fix it.
>> > >>
>> > >> - Jark Wu
>> > >>
>> > >>> 在 2016年10月26日,下午8:09,Till Rohrmann <trohrmann@apache.org>
写道:
>> > >>>
>> > >>> +1 for the features to include.
>> > >>>
>> > >>> What is the state of the Trigger DSL? How much is left to be done
>> > before
>> > >>> merging?
>> > >>>
>> > >>> Cheers,
>> > >>> Till
>> > >>>
>> > >>> On Tue, Oct 25, 2016 at 4:32 PM, Aljoscha Krettek <
>> aljoscha@apache.org
>> > >
>> > >>> wrote:
>> > >>>
>> > >>>> +1 the schedule proposed so far.
>> > >>>>
>> > >>>> Do we also want to get in the "Trigger DSL" that we've had
brewing
>> > for a
>> > >>>> while now?
>> > >>>>
>> > >>>> On Mon, 17 Oct 2016 at 16:17 Stephan Ewen <sewen@apache.org>
>> wrote:
>> > >>>>
>> > >>>>> I think this sounds very reasonable, +1 to the schedule.
>> > >>>>>
>> > >>>>> I would definitely add
>> > >>>>> - FLIP-10 (unify checkpoints and savepoints)
>> > >>>>> - FLIP-7 (metrics in web UI)
>> > >>>>> - FLIP-12 (async request operators)
>> > >>>>>
>> > >>>>> Those should be all safe bets, as they are basically done.
>> > >>>>>
>> > >>>>> Let's see what else is in shape until the feature freeze
day.
>> > >>>>>
>> > >>>>>
>> > >>>>>
>> > >>>>> On Mon, Oct 17, 2016 at 2:18 PM, Fabian Hueske <fhueske@gmail.com
>> >
>> > >>>> wrote:
>> > >>>>>
>> > >>>>>> Hi everybody,
>> > >>>>>>
>> > >>>>>> Flink 1.1.0 was released in August and I think it is
time to kick
>> > off
>> > >> a
>> > >>>>>> discussion about the schedule and scope of Flink 1.2.0.
>> > >>>>>>
>> > >>>>>> == Scope
>> > >>>>>>
>> > >>>>>> We started to collect features for Flink 1.2.0 in the
Flink
>> Release
>> > >>>> wiki
>> > >>>>>> page [1].
>> > >>>>>> I copy the feature list for convenience:
>> > >>>>>>
>> > >>>>>>  - Dynamic Scaling / Key Groups (FLINK-3755
>> > >>>>>>  <https://issues.apache.org/jira/browse/FLINK-3755>)
(Design Doc
>> > >>>>>>  <https://docs.google.com/document/d/1G1OS1z3xEBOrYD4wSu-
>> > >>>>>> LuBCyPUWyFd9l3T9WyssQ63w/edit#heading=h.2suhu1fjxmp4>
>> > >>>>>>  )
>> > >>>>>>  - Rescalable Non-Partitioned State (FLIP-8
>> > >>>>>>  <https://cwiki.apache.org/confluence/display/FLINK/FLIP-
>> > >>>>>> 8%3A+Rescalable+Non-Partitioned+State>
>> > >>>>>>  )
>> > >>>>>>  - Backwards compatible savepoints (FLINK-4797
>> > >>>>>>  <https://issues.apache.org/jira/browse/FLINK-4797>)
>> > >>>>>>  -
>> > >>>>>>
>> > >>>>>>  Integrate Flink with Apache Mesos (FLINK-1984
>> > >>>>>>  <https://issues.apache.org/jira/browse/FLINK-1984>)
(Design Doc
>> > >>>>>>  <https://docs.google.com/document/d/1WItafBmGbjlaBbP8Of5PAFO
>> H9GUJQ
>> > >>>>>> xf5S4hjEuPchuU/edit#heading=h.33uxp8abvuf0>
>> > >>>>>>  )
>> > >>>>>>  - Secure Data Access (FLINK-3930
>> > >>>>>>  <https://issues.apache.org/jira/browse/FLINK-3930>)
(Design Doc
>> > >>>>>>  <https://docs.google.com/document/d/1-
>> > >>>> GQB6uVOyoaXGwtqwqLV8BHDxWiMO2W
>> > >>>>>> nVzBoJ8oPaAs/edit#heading=h.dr22iualfm0h>
>> > >>>>>>  )
>> > >>>>>>  - Queryable State (FLINK-3779
>> > >>>>>>  <https://issues.apache.org/jira/browse/FLINK-3779>)
>> > >>>>>>  - Metrics in Webinterface (FLIP-7
>> > >>>>>>  <https://cwiki.apache.org/confluence/display/FLINK/FLIP-
>> > >>>>>> 7%3A+Expose+metrics+to+WebInterface>
>> > >>>>>>  )
>> > >>>>>>  - Kafka 0.10 support (FLINK-4035
>> > >>>>>>  <http://issues.apache.org/jira/browse/FLINK-4035>)
>> > >>>>>>  - Table API: Group Window Aggregates (FLINK-4691,
FLIP-11)
>> > >>>>>>  - Table API: Scalar Functions (FLINK-3097)
>> > >>>>>>
>> > >>>>>>
>> > >>>>>> Is a feature missing or something too ambitious?
>> > >>>>>>
>> > >>>>>> == Schedule
>> > >>>>>>
>> > >>>>>> In my opinion we should try to release 1.2.0 before
Christmas.
>> That
>> > >>>>> means,
>> > >>>>>> we should have a RC1 by end November / early December
and a
>> feature
>> > >>>>> freeze
>> > >>>>>> two weeks earlier in mid of November. Does that sound
>> appropriate or
>> > >>>>> should
>> > >>>>>> we aim for an earlier or later release?
>> > >>>>>>
>> > >>>>>> What do others think about the scope and schedule?
>> > >>>>>> Please discuss.
>> > >>>>>>
>> > >>>>>> Best,
>> > >>>>>> Fabian
>> > >>>>>>
>> > >>>>>> [1]
>> > >>>>>> https://cwiki.apache.org/confluence/display/FLINK/
>> > >>>>>> Flink+Release+and+Feature+Plan
>> > >>>>>>
>> > >>>>>
>> > >>>>
>> > >>
>> > >>
>> >
>> >
>>
>
>
>

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