Great, thanks! It was fast :)
I will try to check it out in the afternoon!
Gyula
On Fri, Jan 23, 2015 at 11:37 AM, Ufuk Celebi u...@apache.org wrote:
On 22 Jan 2015, at 18:10, Stephan Ewen se...@apache.org wrote:
So the crux is that the JobManager has a location for the sender task
(and
On 22 Jan 2015, at 11:37, Till Rohrmann trohrm...@apache.org wrote:
I'm not sure whether it is currently possible to schedule first the
receiver and then the sender. Recently, I had to fix the
TaskManagerTest.testRunWithForwardChannel test case where this was exactly
the case. Due to first
Thank you! I will play around with it.
On Wed, Jan 21, 2015 at 3:50 PM, Ufuk Celebi u...@apache.org wrote:
Hey Gyula,
On 21 Jan 2015, at 15:41, Gyula Fóra gyf...@apache.org wrote:
Hey Guys,
I think it would make sense to turn lazy operator execution off for
streaming programs because
I think that this is a fairly delicate thing.
The execution graph / scheduling is the most delicate part of the system. I
would not feel too well about a quick fix there, so let's think this
through a little bit.
The logic currently does the following:
1) It schedules the sources (see
Hey Guys,
I think it would make sense to turn lazy operator execution off for
streaming programs because it would make life simpler for windowing. I
also created a JIRA issue here
https://issues.apache.org/jira/browse/FLINK-1425.
Can anyone give me some quick pointers how to do this? Its
