Re: [Documentation] Broken links

2015-05-11 Thread Stephan Ewen
Great, thanks a lot! On Thu, May 7, 2015 at 10:18 PM, Andra Lungu wrote: > Hi Robert, > > Sorry I did not think of doing something like that before :) > https://github.com/apache/flink/pull/662 > > I tend to do lazy evaluation, insist a little bit more next time you see > something I could help

Re: [Documentation] Broken links

2015-05-07 Thread Andra Lungu
Hi Robert, Sorry I did not think of doing something like that before :) https://github.com/apache/flink/pull/662 I tend to do lazy evaluation, insist a little bit more next time you see something I could help out with! Andra On Thu, May 7, 2015 at 11:20 AM, Robert Metzger wrote: > Hey Andra, >

Re: [Documentation] Broken links

2015-05-07 Thread Robert Metzger
Hey Andra, if you want, you can also fix the broken links yourself and open a pull request with the fixes. The documentation is located in the docs/ folder. There is also a bash script which allows you to preview the changes locally (on localhost:4000) ... once you have installed jekyll. On Fri

Re: [Documentation] Broken links

2015-04-24 Thread Stephan Ewen
Hi! I think this refers only to the classes in the previous "compiler", now "optimizer" project. That happened during a refactoring. Sorry about that. I'll try to get to some time in the next days... Greetings, Stephan On Fri, Apr 24, 2015 at 5:00 PM, Andra Lungu wrote: > Hey everyone, > > I

[Documentation] Broken links

2015-04-24 Thread Andra Lungu
Hey everyone, I was following the documentation on how to create a new runtime operator and I noticed that all the links to the classes on Github return 404. http://ci.apache.org/projects/flink/flink-docs-master/internals/add_operator.html Eventually, I started to check the code out directly fro