On the streaming side: Must have: * Tests for the fault tolerance (My first priority this week) * Merging Gyula's recent windowing PR [1]
Really needed: * Self-join for DataStreams (Gabor has a prototype, PR coming today) [1] * ITCase tests for streaming examples (Peter & myself, review and clean up pending) [3] * Different streaming/batch cluster memory settings (Stephan) [4] * Make projection operator chainable (Gabor Gevay - a wannabe GSoC student, PR coming soon) [5] * Parallel time discretization (Gyula, PR coming tomorrow) [6] Would be nice to have: * Complex integration test for streaming (Peter) [7] * Extend streaming aggregation tests to include POJOs [8] * Iteration bug for large input [9] We would also need a general pass over the streaming API for javadocs. This is not one week but we can hopefully fit into two weeks. [1] https://github.com/apache/flink/pull/465 [2] https://issues.apache.org/jira/browse/FLINK-1594 [3] https://issues.apache.org/jira/browse/FLINK-1560 [4] https://issues.apache.org/jira/browse/FLINK-1368 [5] https://issues.apache.org/jira/browse/FLINK-1641 [6] https://issues.apache.org/jira/browse/FLINK-1618 [7] https://issues.apache.org/jira/browse/FLINK-1595 [8] https://issues.apache.org/jira/browse/FLINK-1544 [9] https://issues.apache.org/jira/browse/FLINK-1239 On Tue, Mar 10, 2015 at 11:20 AM, Robert Metzger <rmetz...@apache.org> wrote: > Hey, > > whats the status on this? There is one week left until we are going to fork > off a branch for 0.9 .. if we stick to the suggested timeline. > The initial email said "I am very much in favor of doing this, under the > strong condition that we > are very confident that the master has grown to be stable enough". I think > it is time to evaluate whether we are confident that the master is stable. > > Best > Robert > > > > On Wed, Mar 4, 2015 at 9:42 AM, Robert Metzger <rmetz...@apache.org> > wrote: > > > +1 for Marton as a release manager. Thank you! > > > > > > On Tue, Mar 3, 2015 at 7:56 PM, Henry Saputra <henry.sapu...@gmail.com> > > wrote: > > > >> Ah, thanks Márton. > >> > >> So we are chartering to the similar concept of Spark RRD staging > >> execution =P > >> I suppose there will be a runtime configuration or hint to tell the > >> Flink Job manager to indicate which execution is preferred? > >> > >> > >> - Henry > >> > >> On Tue, Mar 3, 2015 at 2:09 AM, Márton Balassi < > balassi.mar...@gmail.com> > >> wrote: > >> > Hi Henry, > >> > > >> > Batch mode is a new execution mode for batch Flink jobs where instead > of > >> > pipelining the whole execution the job is scheduled in stages, thus > >> > materializing the intermediate result before continuing to the next > >> > operators. For implications see [1]. > >> > > >> > [1] http://www.slideshare.net/KostasTzoumas/flink-internals, page > >> 18-21. > >> > > >> > > >> > On Mon, Mar 2, 2015 at 11:39 PM, Henry Saputra < > henry.sapu...@gmail.com > >> > > >> > wrote: > >> > > >> >> HI Stephan, > >> >> > >> >> What is "Batch mode" feature in the list? > >> >> > >> >> - Henry > >> >> > >> >> On Mon, Mar 2, 2015 at 5:03 AM, Stephan Ewen <se...@apache.org> > wrote: > >> >> > Hi all! > >> >> > > >> >> > ApacheCon is coming up and it is the 15th anniversary of the Apache > >> >> > Software Foundation. > >> >> > > >> >> > In the course of the conference, Apache would like to make a series > >> of > >> >> > announcements. If we manage to make a release during (or shortly > >> before) > >> >> > ApacheCon, they will announce it through their channels. > >> >> > > >> >> > I am very much in favor of doing this, under the strong condition > >> that we > >> >> > are very confident that the master has grown to be stable enough > >> (there > >> >> are > >> >> > major changes in the distributed runtime since version 0.8 that we > >> are > >> >> > still stabilizing). No use in a widely announced build that does > not > >> have > >> >> > the quality. > >> >> > > >> >> > Flink has now many new features that warrant a release soon (once > we > >> >> fixed > >> >> > the last quirks in the new distributed runtime). > >> >> > > >> >> > Notable new features are: > >> >> > - Gelly > >> >> > - Streaming windows > >> >> > - Flink on Tez > >> >> > - Expression API > >> >> > - Distributed Runtime on Akka > >> >> > - Batch mode > >> >> > - Maybe even a first ML library version > >> >> > - Some streaming fault tolerance > >> >> > > >> >> > Robert proposed to have a feature freeze mid Match for that. His > >> >> > cornerpoints were: > >> >> > > >> >> > Feature freeze (forking off "release-0.9"): March 17 > >> >> > RC1 vote: March 24 > >> >> > > >> >> > The RC1 vote is 20 days before the ApacheCon (13. April). > >> >> > For the last three releases, the average voting time was 20 days: > >> >> > R 0.8.0 --> 14 days > >> >> > R 0.7.0 --> 22 days > >> >> > R 0.6 --> 26 days > >> >> > > >> >> > Please share your opinion on this! > >> >> > > >> >> > > >> >> > Greetings, > >> >> > Stephan > >> >> > >> > > > > >
