[jira] [Created] (FLINK-1545) Spurious failure of AsynchronousFileIOChannelsTest.testExceptionForwardsToClose

2015-02-14 Thread Till Rohrmann (JIRA)
Till Rohrmann created FLINK-1545: Summary: Spurious failure of AsynchronousFileIOChannelsTest.testExceptionForwardsToClose Key: FLINK-1545 URL: https://issues.apache.org/jira/browse/FLINK-1545 Project

Streaming Windowing rework (runtime + api)

2015-02-14 Thread Gyula Fóra
Hey, I have opened a PR for the windowing rework I have been doing in the last couple of weeks. It introduces several new abstractions for the windowing semantics along with optional global/local discretisation logics and greatly improved performance using pre-aggregators https://github.com/apach

Measuring Iteration Timings

2015-02-14 Thread Kirschnick, Johannes
Hi, I have a simple question on to how one could measure the individual execution times for an iteration step, without parsing the logs :) Is there a best practise for that? I'm interested in producing something like this http://data-artisans.com/img/blog/bulk_runtimes.png >From the blog

Re: Measuring Iteration Timings

2015-02-14 Thread Robert Metzger
Hi, Right now, you have to parse the logs (of the TaskManager running the Sync Task). We've created the linked images using this (very hacky) tool: https://github.com/project-flink/flink-perf/blob/master/flink-jobs/src/main/java/com/github/projectflink/utils/IterationParser.java . I'm currently w

Re: Measuring Iteration Timings

2015-02-14 Thread Kirschnick, Johannes
Hi, thanks for the quick answer - this tool might just do the job for the moment. Johannes Von: Robert Metzger Gesendet: Samstag, 14. Februar 2015 16:38 An: dev@flink.apache.org Betreff: Re: Measuring Iteration Timings Hi, Right now, you have to parse t

Re: Measuring Iteration Timings

2015-02-14 Thread Stephan Ewen
Johannes! You can also customize your messages by printing a message to standard out in the open() and close() methods of your functions. You have to extend the RichFunction in that case. Greetings, Stephan On Sat, Feb 14, 2015 at 4:47 PM, Kirschnick, Johannes < johannes.kirschn...@tu-berlin.de

[jira] [Created] (FLINK-1546) Failed job causes JobManager to shutdown due to uncatched WebFrontend exception

2015-02-14 Thread Robert Metzger (JIRA)
Robert Metzger created FLINK-1546: - Summary: Failed job causes JobManager to shutdown due to uncatched WebFrontend exception Key: FLINK-1546 URL: https://issues.apache.org/jira/browse/FLINK-1546 Proje

[jira] [Created] (FLINK-1547) Disable automated ApplicationMaster restart

2015-02-14 Thread Robert Metzger (JIRA)
Robert Metzger created FLINK-1547: - Summary: Disable automated ApplicationMaster restart Key: FLINK-1547 URL: https://issues.apache.org/jira/browse/FLINK-1547 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-1548) [DISCUSS] Make Scala implicit parameters explicit in the runtime

2015-02-14 Thread Stephan Ewen (JIRA)
Stephan Ewen created FLINK-1548: --- Summary: [DISCUSS] Make Scala implicit parameters explicit in the runtime Key: FLINK-1548 URL: https://issues.apache.org/jira/browse/FLINK-1548 Project: Flink

[DISCUSS] Scala code style - explicit vs implicit code behavior

2015-02-14 Thread Stephan Ewen
Hi everyone! Since a sizable portion of the Flink code is now in Scala (and more is coming in the API projects), I think we need to define a few guidelines for Scala programming. Scala is very powerful and has a lot of "magic" features that allow you to design killer nice APIs, but also make reas

[Gelly]Distributed Minimum Spanning Tree Example

2015-02-14 Thread Andra Lungu
Hey guys, As I previously said, I have had some problems getting this DMST algorithm to be fully functional, either with Flink 0.8 or with Flink 0.9. My latest problem(and I have been debugging this for quite some days) was that for the test I wrote that extended MultipleProgramsTestBase, the Exe

Re: [DISCUSS] Scala code style - explicit vs implicit code behavior

2015-02-14 Thread Henry Saputra
+1 to the idea I suppose no really action item for FLINK-1548? Maybe add doc about contributing to Scala portion? On Saturday, February 14, 2015, Stephan Ewen wrote: > Hi everyone! > > Since a sizable portion of the Flink code is now in Scala (and more is > coming in the API projects), I think

Re: [Gelly]Distributed Minimum Spanning Tree Example

2015-02-14 Thread Fabian Hueske
Hi Andra, I haven't had a detailed look at Gelly and its functions, but Flink has only few operators which can cause undeterministic behavior. In general, user code should be implemented without side effects, i.e., the result of each function call may only depend on its arguments. This principle g

[jira] [Created] (FLINK-1549) Add proper exception handling for YarnJobManager

2015-02-14 Thread Till Rohrmann (JIRA)
Till Rohrmann created FLINK-1549: Summary: Add proper exception handling for YarnJobManager Key: FLINK-1549 URL: https://issues.apache.org/jira/browse/FLINK-1549 Project: Flink Issue Type: Bu