flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aljoscha Krettek <aljos...@apache.org>
Subject Re: [DISCUSS] FLIP-1 : Fine grained recovery from task failures
Date Wed, 13 Jul 2016 15:17:53 GMT
+1
This was my original motivation. I saw a lot of discussion on the design
docs I initiated but none of this was reflected on the ML.

On Wed, 13 Jul 2016 at 17:11 Robert Metzger <rmetzger@apache.org> wrote:

> Thank you for writing the proposal!
>
> I agree with Chesnay. I thought one of the main motivations of the new FLIP
> process is to move the discussion onto ASF infra, to record the decision
> making process on the mailing list and to make ongoing activities more
> visible to the community.
>
> If we want to use google docs because of the commenting features, we should
> consider implementing a tool mirroring the comments onto the mailing lists.
>
> If you want to change the FLIP process, I would suggest to move the
> discussion about Google Docs to the FLIP 1 thread.
>
>
>
> On Wed, Jul 13, 2016 at 2:07 PM, Stephan Ewen <sewen@apache.org> wrote:
>
> > I deliberately kept it initially in the Google Doc because it is easier
> to
> > comment.
> >
> > I would move it to the wiki once we have passed the initial discussion
> and
> > have converged (or are close to convergence) on the design.
> >
> > On Tue, Jul 12, 2016 at 8:11 PM, Chesnay Schepler <chesnay@apache.org>
> > wrote:
> >
> > > shouldn't the proposal be contained in the wiki instead of GoogleDocs?
> > >
> > >
> > > On 12.07.2016 19:55, Stephan Ewen wrote:
> > >
> > >> Hi all!
> > >>
> > >> Here is the very first FLIP (FLink Improvement Proposal): Fine grained
> > >> recovery from task failures
> > >>
> > >> It describes a proposed enhancement for reducing the work done during
> > >> recovery.
> > >>
> > >>
> > >>
> >
> https://docs.google.com/document/d/16S584XFzkfFu3MOfVCE0rHZ_JJgQrQuw9SXpanoMiMo
> > >>
> > >> Please comment in this mail thread, or in the GoogleDoc.
> > >>
> > >> Best,
> > >> Stephan
> > >>
> > >>
> > >
> >
>

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