+1 I think the changes are good. Thanks!
On Sun, Apr 10, 2016 at 2:34 PM, Matthias J. Sax <mj...@apache.org> wrote: > Done. > > This is a preview: https://github.com/mjsax/flink-web/tree/broken-links > > Please let me know if I can push it. (Maybe someone can verify, that I > did not miss anything...) > > -Matthias > > > On 04/07/2016 04:41 PM, Stephan Ewen wrote: >> Hey Matthias! >> >> The mailing list and feature requests are getting super many, hard to keep >> up and fix things within days... >> >> Do you think you could fix those links? As a simple approach, I would >> suggest to >> >> - Truncate the history to drop everything earlier than "Flink" days (in >> your list before Hadoop Compatibility in Flink) >> >> - Links that point to a changing URL (docs-master or Github master >> branch) to point to the release around that time. >> >> - Links from news that have no match any more should probably be >> dropped... >> >> Stephan >> >> >> >> On Thu, Apr 7, 2016 at 2:54 PM, Matthias J. Sax <mj...@apache.org> wrote: >> >>> Anyone? >>> >>> On 04/04/2016 05:06 PM, Matthias J. Sax wrote: >>>> Hi, >>>> >>>> I just stepped through the whole blog. Some stuff can get fixed easily, >>>> more links should just be removed, and for some I am not sure what to do >>>> about (quite old stuff). >>>> >>>> I put my though about each broken link (or nothing if I have no idea how >>>> to deal with it). Please give feedback. >>>> >>>> >>>> >>>> ** Version 0.2 Released >>>> -> Link zum Changelog: >>>> https://stratosphere.eu/wiki/doku.php/wiki:changesrelease0.2 >>>> >>>> >>>> >>>> ** Stratosphere Demo Accepted for ICDE 2013 -> links zum Paper und poster >>>> -> >>>> >>> https://flink.apache.org/assets/papers/optimizationOfDataFlowsWithUDFs_13.pdf >>>> -> >>>> >>> https://flink.apache.org/assets/papers/optimizationOfDataFlowsWithUDFs_poster_13.pdf >>>> >>>> Paper: >>> http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6544927 >>>> Poster not sure (maybe ask Fabian or remove link) >>>> >>>> >>>> >>>> ** Stratosphere Demo Paper Accepted for BTW 2013 >>>> -> https://flink.apache.org/assets/papers/Sopremo_Meteor%20BigData.pdf >>>> >>>> >>>> >>>> ** ICDE 2013 Demo Preview >>>> -> https://flink.apache.org/publications >>>> >>>> This section does no exist any more. But the paper is linked in another >>>> blog post anyway. Maybe, we can remove the whole blog post. >>>> >>>> >>>> >>>> ** Paper "All Roads Lead to Rome: Optimistic Recovery for Distributed >>>> Iterative Data Processing" accepted at CIKM 2013 >>>> -> https://flink.apache.org/assets/papers/optimistic.pdf >>>> >>>> Available at https://dl.acm.org/citation.cfm?doid=2505515.2505753 >>>> >>>> >>>> >>>> ** Stratosphere got accepted to the Hadoop Summit Europe in Amsterdam >>>> -> http://hadoopsummit.org/amsterdam/ >>>> -> >>>> >>> https://hadoopsummit.uservoice.com/forums/196822-future-of-apache-hadoop/filters/top >>>> >>>> I would just remove those links. >>>> >>>> >>>> >>>> ** Stratosphere 0.4 Released >>>> -> >>>> >>> https://flink.apache.org/blog/tutorial/2014/01/12/0.4-migration-guide.html >>>> -> >>>> >>> https://flink.apache.org/blog/tutorial/2014/01/12/0.4-migration-guide.html >>>> -> >>>> >>> https://ci.apache.org/projects/flink/flink-docs-master/0.4/programming_guides/iterations.html >>>> -> >>>> >>> https://ci.apache.org/projects/flink/flink-docs-master/0.4/programming_guides/iterations.html >>>> -> >>>> >>> https://ci.apache.org/projects/flink/flink-docs-master/0.4/program_execution/local_executor.html >>>> -> https://flink.apache.org/quickstart/ >>>> >>>> >>>> >>>> >>>> ** Optimizer Plan Visualization Tool >>>> -> http://stratosphere.eu/docs/0.4/program_execution/web_interface.html >>>> -> http://stratosphere.eu/docs/0.4/program_execution/local_executor.html >>>> >>>> >>>> >>>> ** Use Stratosphere with Amazon Elastic MapReduce >>>> -> >>>> >>> https://ci.apache.org/projects/flink/flink-docs-master/0.4/setup/yarn.html >>>> >>>> >>>> >>>> ** Stratosphere version 0.5 available >>>> -> http://stratosphere.eu/docs/0.5/ >>>> -> http://stratosphere.eu/docs/0.5/programming_guides/examples_java.html >>>> >>>> >>>> >>>> ** Hadoop Compatibility in Flink >>>> -> >>>> >>> https://ci.apache.org/projects/flink/flink-docs-release-0.7/hadoop_compatibility.html >>>> >>>> Works; however, we might want to point to a newer version (maybe current >>>> master?) >>>> >>>> >>>> >>>> ** January 2015 in the Flink community >>>> -> http://data-artisans.com/computing-recommendations-with-flink.html >>>> -> >>>> >>> http://2015.hadoopsummit.org/amsterdam-blog/announcing-the-community-vote-session-winners-for-the-2015-hadoop-summit-europe/ >>>> >>>> >>>> >>>> ** Introducing Flink Streaming >>>> -> >>>> >>> http://ci.apache.org/projects/flink/flink-docs-master/apis/streaming_guide.html#sources >>>> -> >>>> >>> http://ci.apache.org/projects/flink/flink-docs-master/apis/streaming_guide.html#stream-connectors >>>> -> >>>> >>> http://ci.apache.org/projects/flink/flink-docs-master/apis/streaming_guide.html#window-operators >>>> >>>> Those can be fixed easily (point to current master) >>>> >>>> >>>> >>>> ** February 2015 in the Flink community >>>> -> >>>> >>> https://github.com/apache/flink/tree/master/flink-staging/flink-gelly/src/main/java/org/apache/flink/graph/example >>>> -> https://github.com/apache/flink/tree/master/flink-staging/flink-table >>>> -> >>> https://github.com/apache/flink/tree/master/flink-staging/flink-hcatalog >>>> >>>> I would just removed those. >>>> >>>> >>>> >>>> ** Peeking into Apache Flink's Engine Room >>>> -> >>>> >>> https://ci.apache.org/projects/flink/flink-docs-master/apis/dataset_transformations.html#join-algorithm-hints >>>> >>>> Can be fixed with >>>> >>> https://ci.apache.org/projects/flink/flink-docs-master/apis/batch/index.html#semantic-annotations >>>> >>>> >>>> >>>> ** March 2015 in the Flink community >>>> -> http://data-artisans.com/dataflow.html >>>> -> https://github.com/apache/flink/tree/master/flink-staging/flink-table >>>> -> >>>> >>> https://github.com/apache/flink/blob/master/flink-staging/flink-table/src/main/java/org/apache/flink/examples/java/JavaTableExample.java >>>> -> >>>> >>> https://github.com/apache/flink/tree/master/flink-staging/flink-table/src/main/scala/org/apache/flink/examples/scala >>>> -> https://github.com/apache/flink/tree/master/flink-staging/flink-ml >>>> -> >>>> >>> https://ci.apache.org/projects/flink/flink-docs-master/setup/flink_on_tez.html >>>> >>>> >>>> >>>> ** Announcing Flink 0.9.0-milestone1 preview release >>>> -> >>>> >>> https://ci.apache.org/projects/flink/flink-docs-master/apis/iterations.html >>>> >>>> Can be fixed easily. >>>> >>>> >>>> >>>> ** Announcing Flink Forward 2015 >>>> All links broken... >>>> >>>> >>>> >>>> ** Off-heap Memory in Apache Flink and the curious JIT compiler >>>> -> >>>> >>> https://github.com/apache/flink/blob/master/flink-core/src/test/java/org/apache/flink/core/memory/benchmarks/MemorySegmentSpeedBenchmark.java >>>> >>>> >>>> >>>> ** Storm Compatibility in Apache Flink: How to run existing Storm >>>> topologies on Flink >>>> -> >>>> >>> https://ci.apache.org/projects/flink/flink-docs-master/apis/storm_compatibility.html >>>> >>>> Can be fixed easily. >>>> >>>> >>>> >>>> ** Flink Forward 2015 >>>> -> http://flink-forward.org/ point to FF16 now >>>> -> http://flink-forward.org/?post_type=day >>>> >>>> >>>> >>>> Just let me know what you think about it. >>>> >>>> >>>> -Matthias >>>> >>>> >>>> On 04/04/2016 03:46 PM, Ufuk Celebi wrote: >>>>> Hey Matthias, >>>>> >>>>> could you update the links in the posts or share a list of the posts >>>>> with broken links so I can update them? >>>>> >>>>> We can also provide redirects for the broken links. With 1.0, we now >>>>> should be more careful to not break/redirect links... >>>>> >>>>> >>>>> On Mon, Apr 4, 2016 at 2:53 PM, Matthias J. Sax <mj...@apache.org> >>> wrote: >>>>>> Hi, >>>>>> >>>>>> I just realized, that the restructuring of the programming guide in our >>>>>> documentation >>>>>> >>> https://github.com/apache/flink/commit/ad267a4b199979536dd8a5572628eefc77d7e0f4 >>> ) >>>>>> broke a couple of links from the Flink blog. >>>>>> >>>>>> Should we update those older blog post? JIRA for it? >>>>>> >>>>>> For the future: would it be a good idea to maintain a "link directory" >>>>>> to keep track of used links that must be updated in case of a similar >>>>>> doc change in the future (for links that point to current master docs)? >>>>>> >>>>>> >>>>>> >>>>>> -Matthias >>>>>> >>>> >>> >>> >> >
