Re: [MultipleProgramsTestBase][Cluster vs. Collection mode] Inconsistent Behavior

2015-03-04 Thread Vasiliki Kalavri
Thanks! I created an issue [1] and will try to look into this during the weekend (unless someone gets to it faster :)) Cheers, V. [1]: http://issues.apache.org/jira/browse/FLINK-1652 On 4 March 2015 at 20:29, Stephan Ewen wrote: > My gut feeling would be that the IterationRuntimeContext shoul

Re: [MultipleProgramsTestBase][Cluster vs. Collection mode] Inconsistent Behavior

2015-03-04 Thread Stephan Ewen
My gut feeling would be that the IterationRuntimeContext should be the same across all iterations. It only needs to support returning a different superstep number in each superstep. On Wed, Mar 4, 2015 at 7:13 PM, Vasiliki Kalavri wrote: > Hi, > > I have found the issue, but will need some help

Re: [MultipleProgramsTestBase][Cluster vs. Collection mode] Inconsistent Behavior

2015-03-04 Thread Vasiliki Kalavri
Hi, I have found the issue, but will need some help to resolve it :) In CollectionExecutor, if the superstep number is > 0 (I guess this means iteration?) a new IterationRuntimeUDFContext is created for every unary and binary operator, being assigned this superstep number in its constructor. How

Re: [MultipleProgramsTestBase][Cluster vs. Collection mode] Inconsistent Behavior

2015-03-04 Thread Vasiliki Kalavri
Hi Andra, judging from the output, it seems that all 3 supersteps are executed in the second case as well, but getSuperstepNumber() is returning the wrong superstep number. I confirmed that this is also the case in VertexCentricConnectedComponentsITCase and SpargelConnectedComponentsITCase, i.e. t