Hey Stephan,
Thanks for looking into it!
+1 for breaking this up, will do that.
I can see your point and maybe it makes sense to introduce part of scoping to
incorporate support for nested loops (otherwise it can’t work).
Let us think about this a bit. We will share another draft for a more det
How about we break this up into two FLIPs? There are after all two
orthogonal problems (termination, fault tolerance) with quite different
discussion states.
Concerning fault tolerance, I like the ideas.
For the termination proposal, I would like to iterate a bit more.
*Termination algorithm:*
M
Hi!
I am still scanning it and compiling some comments. Give me a bit ;-)
Stephan
On Wed, Oct 26, 2016 at 6:13 PM, Paris Carbone wrote:
> Hey all,
>
> Now that many of you have already scanned the document (judging from the
> views) maybe it is time to give back some feedback!
> Did you like
Hey all,
Now that many of you have already scanned the document (judging from the views)
maybe it is time to give back some feedback!
Did you like it? Would you suggest an improvement?
I would suggest not to leave this in the void. It has to do with important
properties that the system promises
Hello everyone,
Loops in Apache Flink have a good potential to become a much more powerful
thing in future version of Apache Flink.
There is generally high demand to make them usable and first of all
production-ready for upcoming releases.
As a first commitment we would like to propose FLIP-13
