http://git-wip-us.apache.org/repos/asf/flink-web/blob/9ec0a879/content/news/2015/03/02/february-2015-in-flink.html ---------------------------------------------------------------------- diff --git a/content/news/2015/03/02/february-2015-in-flink.html b/content/news/2015/03/02/february-2015-in-flink.html new file mode 100644 index 0000000..1e3a09b --- /dev/null +++ b/content/news/2015/03/02/february-2015-in-flink.html @@ -0,0 +1,308 @@ +<!DOCTYPE html> +<html lang="en"> + <head> + <meta charset="utf-8"> + <meta http-equiv="X-UA-Compatible" content="IE=edge"> + <meta name="viewport" content="width=device-width, initial-scale=1"> + <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags --> + <title>Apache Flink: February 2015 in the Flink community</title> + <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon"> + <link rel="icon" href="/favicon.ico" type="image/x-icon"> + + <!-- Bootstrap --> + <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap.min.css";> + <link rel="stylesheet" href="/css/flink.css"> + <link rel="stylesheet" href="/css/syntax.css"> + + <!-- Blog RSS feed --> + <link href="/blog/feed.xml" rel="alternate" type="application/rss+xml" title="Apache Flink Blog: RSS feed" /> + + <!-- jQuery (necessary for Bootstrap's JavaScript plugins) --> + <!-- We need to load Jquery in the header for custom google analytics event tracking--> + <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.2/jquery.min.js";></script> + + <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries --> + <!-- WARNING: Respond.js doesn't work if you view the page via file:// --> + <!--[if lt IE 9]> + <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js";></script> + <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js";></script> + <![endif]--> + </head> + <body> + + + <!-- Main content. --> + <div class="container"> + <div class="row"> + + + <div id="sidebar" class="col-sm-3"> + <!-- Top navbar. --> + <nav class="navbar navbar-default"> + <!-- The logo. --> + <div class="navbar-header"> + <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1"> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + </button> + <div class="navbar-logo"> + <a href="/"> + <img alt="Apache Flink" src="/img/navbar-brand-logo.png" width="147px" height="73px"> + </a> + </div> + </div><!-- /.navbar-header --> + + <!-- The navigation links. --> + <div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1"> + <ul class="nav navbar-nav navbar-main"> + + <!-- Downloads --> + <li class=""><a class="btn btn-info" href="/downloads.html">Download Flink</a></li> + + <!-- Overview --> + <li><a href="/index.html">Home</a></li> + + <!-- Intro --> + <li><a href="/introduction.html">Introduction to Flink</a></li> + + <!-- Use cases --> + <li><a href="/usecases.html">Flink Use Cases</a></li> + + <!-- Powered by --> + <li><a href="/poweredby.html">Powered by Flink</a></li> + + <!-- Ecosystem --> + <li><a href="/ecosystem.html">Ecosystem</a></li> + + <!-- Community --> + <li><a href="/community.html">Community & Project Info</a></li> + + <!-- Contribute --> + <li><a href="/how-to-contribute.html">How to Contribute</a></li> + + <!-- Blog --> + <li class=" active hidden-md hidden-sm"><a href="/blog/"><b>Flink Blog</b></a></li> + + <hr /> + + + + <!-- Documentation --> + <!-- <li> + <a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1"; target="_blank">Documentation <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> --> + <li class="dropdown"> + <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation + <span class="caret"></span></a> + <ul class="dropdown-menu"> + <li><a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1"; target="_blank">1.1 (Latest stable release) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + <li><a href="http://ci.apache.org/projects/flink/flink-docs-release-1.2"; target="_blank">1.2 (Snapshot) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + </ul> + </li> + + <!-- Quickstart --> + <li> + <a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1/quickstart/setup_quickstart.html"; target="_blank">Quickstart <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> + + <!-- GitHub --> + <li> + <a href="https://github.com/apache/flink"; target="_blank">Flink on GitHub <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> + + + + + + + </ul> + + + + <ul class="nav navbar-nav navbar-bottom"> + <hr /> + + <!-- FAQ --> + <li ><a href="/faq.html">Project FAQ</a></li> + + <!-- Twitter --> + <li><a href="https://twitter.com/apacheflink"; target="_blank">@ApacheFlink <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + + <!-- Visualizer --> + <li class=" hidden-md hidden-sm"><a href="/visualizer/" target="_blank">Plan Visualizer <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + + </ul> + </div><!-- /.navbar-collapse --> + </nav> + + </div> + <div class="col-sm-9"> + <div class="row-fluid"> + <div class="col-sm-12"> + <div class="row"> + <h1>February 2015 in the Flink community</h1> + + <article> + <p>02 Mar 2015</p> + +<p>February might be the shortest month of the year, but this does not +mean that the Flink community has not been busy adding features to the +system and fixing bugs. Hereâs a rundown of the activity in the Flink +community last month.</p> + +<h3 id="release">0.8.1 release</h3> + +<p>Flink 0.8.1 was released. This bugfixing release resolves a total of 22 issues.</p> + +<h3 id="new-committer">New committer</h3> + +<p><a href="https://github.com/mxm";>Max Michels</a> has been voted a committer by the Flink PMC.</p> + +<h3 id="flink-adapter-for-apache-samoa">Flink adapter for Apache SAMOA</h3> + +<p><a href="http://samoa.incubator.apache.org";>Apache SAMOA (incubating)</a> is a +distributed streaming machine learning (ML) framework with a +programming abstraction for distributed streaming ML algorithms. SAMOA +runs on a variety of backend engines, currently Apache Storm and +Apache S4. A <a href="https://github.com/apache/incubator-samoa/pull/11";>pull +request</a> is +available at the SAMOA repository that adds a Flink adapter for SAMOA.</p> + +<h3 id="easy-flink-deployment-on-google-compute-cloud">Easy Flink deployment on Google Compute Cloud</h3> + +<p>Flink is now integrated in bdutil, Googleâs open source tool for +creating and configuring (Hadoop) clusters in Google Compute +Engine. Deployment of Flink clusters in now supported starting with +<a href="https://groups.google.com/forum/#!topic/gcp-hadoop-announce/uVJ_6y9cGKM";>bdutil +1.2.0</a>.</p> + +<h3 id="flink-on-the-web">Flink on the Web</h3> + +<p>A new blog post on <a href="http://flink.apache.org/news/2015/02/09/streaming-example.html";>Flink +Streaming</a> +was published at the blog. Flink was mentioned in several articles on +the web. Here are some examples:</p> + +<ul> + <li> + <p><a href="http://dataconomy.com/how-flink-became-an-apache-top-level-project/";>How Flink became an Apache Top-Level Project</a></p> + </li> + <li> + <p><a href="https://www.linkedin.com/pulse/stale-synchronous-parallelism-new-frontier-apache-flink-nam-luc-tran?utm_content=buffer461af&utm_medium=social&utm_source=linkedin.com&utm_campaign=buffer";>Stale Synchronous Parallelism: The new frontier for Apache Flink?</a></p> + </li> + <li> + <p><a href="http://www.hadoopsphere.com/2015/02/distributed-data-processing-with-apache.html";>Distributed data processing with Apache Flink</a></p> + </li> + <li> + <p><a href="http://www.hadoopsphere.com/2015/02/ciao-latency-hallo-speed.html";>Ciao latency, hello speed</a></p> + </li> +</ul> + +<h2 id="in-the-flink-master">In the Flink master</h2> + +<p>The following features have been now merged in Flinkâs master repository.</p> + +<h3 id="gelly">Gelly</h3> + +<p>Gelly, Flinkâs Graph API allows users to manipulate graph-shaped data +directly. Hereâs for example a calculation of shortest paths in a +graph:</p> + +<div class="highlight"><pre><code class="language-java" data-lang="java"><span class="n">Graph</span><span class="o"><</span><span class="n">Long</span><span class="o">,</span> <span class="n">Double</span><span class="o">,</span> <span class="n">Double</span><span class="o">></span> <span class="n">graph</span> <span class="o">=</span> <span class="n">Graph</span><span class="o">.</span><span class="na">fromDataSet</span><span class="o">(</span><span class="n">vertices</span><span class="o">,</span> <span class="n">edges</span><span class="o">,</span> <span class="n">env</span><span class="o">);</span> + +<span class="n">DataSet</span><span class="o"><</span><span class="n">Vertex</span><span class="o"><</span><span class="n">Long</span><span class="o">,</span> <span class="n">Double</span><span class="o">>></span> <span class="n">singleSourceShortestPaths</span> <span class="o">=</span> <span class="n">graph</span> + <span class="o">.</span><span class="na">run</span><span class="o">(</span><span class="k">new</span> <span class="n">SingleSourceShortestPaths</span><span class="o"><</span><span class="n">Long</span><span class="o">>(</span><span class="n">srcVertexId</span><span class="o">,</span> + <span class="n">maxIterations</span><span class="o">)).</span><span class="na">getVertices</span><span class="o">();</span></code></pre></div> + +<p>See more Gelly examples +<a href="https://github.com/apache/flink/tree/master/flink-libraries/flink-gelly-examples";>here</a>.</p> + +<h3 id="flink-expressions">Flink Expressions</h3> + +<p>The newly merged +<a href="https://github.com/apache/flink/tree/master/flink-libraries/flink-table";>flink-table</a> +module is the first step in Flinkâs roadmap towards logical queries +and SQL support. Hereâs a preview on how you can read two CSV file, +assign a logical schema to, and apply transformations like filters and +joins using logical attributes rather than physical data types.</p> + +<div class="highlight"><pre><code class="language-scala" data-lang="scala"><span class="k">val</span> <span class="n">customers</span> <span class="k">=</span> <span class="n">getCustomerDataSet</span><span class="o">(</span><span class="n">env</span><span class="o">)</span> + <span class="o">.</span><span class="n">as</span><span class="o">(</span><span class="-Symbol">'id</span><span class="o">,</span> <span class="-Symbol">'mktSegment</span><span class="o">)</span> + <span class="o">.</span><span class="n">filter</span><span class="o">(</span> <span class="-Symbol">'mktSegment</span> <span class="o">===</span> <span class="s">"AUTOMOBILE"</span> <span class="o">)</span> + +<span class="k">val</span> <span class="n">orders</span> <span class="k">=</span> <span class="n">getOrdersDataSet</span><span class="o">(</span><span class="n">env</span><span class="o">)</span> + <span class="o">.</span><span class="n">filter</span><span class="o">(</span> <span class="n">o</span> <span class="k">=></span> <span class="n">dateFormat</span><span class="o">.</span><span class="n">parse</span><span class="o">(</span><span class="n">o</span><span class="o">.</span><span class="n">orderDate</span><span class="o">).</span><span class="n">before</span><span class="o">(</span><span class="n">date</span><span class="o">)</span> <span class="o">)</span> + <span class="o">.</span><span class="n">as</span><span class="o">(</span><span class="-Symbol">'orderId</span><span class="o">,</span> <span class="-Symbol">'custId</span><span class="o">,</span> <span class="-Symbol">'orderDate</span><span class="o">,</span> <span class="-Symbol">'shipPrio</span><span class="o">)</span> + +<span class="k">val</span> <span class="n">items</span> <span class="k">=</span> + <span class="n">orders</span><span class="o">.</span><span class="n">join</span><span class="o">(</span><span class="n">customers</span><span class="o">)</span> + <span class="o">.</span><span class="n">where</span><span class="o">(</span><span class="-Symbol">'custId</span> <span class="o">===</span> <span class="-Symbol">'id</span><span class="o">)</span> + <span class="o">.</span><span class="n">select</span><span class="o">(</span><span class="-Symbol">'orderId</span><span class="o">,</span> <span class="-Symbol">'orderDate</span><span class="o">,</span> <span class="-Symbol">'shipPrio</span><span class="o">)</span></code></pre></div> + +<h3 id="access-to-hcatalog-tables">Access to HCatalog tables</h3> + +<p>With the <a href="https://github.com/apache/flink/tree/master/flink-batch-connectors/flink-hcatalog";>flink-hcatalog +module</a>, +you can now conveniently access HCatalog/Hive tables. The module +supports projection (selection and order of fields) and partition +filters.</p> + +<h3 id="access-to-secured-yarn-clustershdfs">Access to secured YARN clusters/HDFS.</h3> + +<p>With this change users can access Kerberos secured YARN (and HDFS) +Hadoop clusters. Also, basic support for accessing secured HDFS with +a standalone Flink setup is now available.</p> + + + </article> + </div> + + <div class="row"> + <div id="disqus_thread"></div> + <script type="text/javascript"> + /* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */ + var disqus_shortname = 'stratosphere-eu'; // required: replace example with your forum shortname + + /* * * DON'T EDIT BELOW THIS LINE * * */ + (function() { + var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true; + dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js'; + (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq); + })(); + </script> + </div> + </div> +</div> + </div> + </div> + + <hr /> + + <div class="row"> + <div class="footer text-center col-sm-12"> + <p>Copyright © 2014-2016 <a href="http://apache.org";>The Apache Software Foundation</a>. All Rights Reserved.</p> + <p>Apache Flink, Apache, and the Apache feather logo are either registered trademarks or trademarks of The Apache Software Foundation.</p> + <p><a href="/privacy-policy.html">Privacy Policy</a> · <a href="/blog/feed.xml">RSS feed</a></p> + </div> + </div> + </div><!-- /.container --> + + <!-- Include all compiled plugins (below), or include individual files as needed --> + <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js";></script> + <script src="/js/codetabs.js"></script> + <script src="/js/stickysidebar.js"></script> + + + <!-- Google Analytics --> + <script> + (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ + (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), + m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) + })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); + + ga('create', 'UA-52545728-1', 'auto'); + ga('send', 'pageview'); + </script> + </body> +</html>
http://git-wip-us.apache.org/repos/asf/flink-web/blob/9ec0a879/content/news/2015/03/13/peeking-into-Apache-Flinks-Engine-Room.html ---------------------------------------------------------------------- diff --git a/content/news/2015/03/13/peeking-into-Apache-Flinks-Engine-Room.html b/content/news/2015/03/13/peeking-into-Apache-Flinks-Engine-Room.html new file mode 100644 index 0000000..9871dd0 --- /dev/null +++ b/content/news/2015/03/13/peeking-into-Apache-Flinks-Engine-Room.html @@ -0,0 +1,379 @@ +<!DOCTYPE html> +<html lang="en"> + <head> + <meta charset="utf-8"> + <meta http-equiv="X-UA-Compatible" content="IE=edge"> + <meta name="viewport" content="width=device-width, initial-scale=1"> + <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags --> + <title>Apache Flink: Peeking into Apache Flink's Engine Room</title> + <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon"> + <link rel="icon" href="/favicon.ico" type="image/x-icon"> + + <!-- Bootstrap --> + <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap.min.css";> + <link rel="stylesheet" href="/css/flink.css"> + <link rel="stylesheet" href="/css/syntax.css"> + + <!-- Blog RSS feed --> + <link href="/blog/feed.xml" rel="alternate" type="application/rss+xml" title="Apache Flink Blog: RSS feed" /> + + <!-- jQuery (necessary for Bootstrap's JavaScript plugins) --> + <!-- We need to load Jquery in the header for custom google analytics event tracking--> + <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.2/jquery.min.js";></script> + + <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries --> + <!-- WARNING: Respond.js doesn't work if you view the page via file:// --> + <!--[if lt IE 9]> + <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js";></script> + <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js";></script> + <![endif]--> + </head> + <body> + + + <!-- Main content. --> + <div class="container"> + <div class="row"> + + + <div id="sidebar" class="col-sm-3"> + <!-- Top navbar. --> + <nav class="navbar navbar-default"> + <!-- The logo. --> + <div class="navbar-header"> + <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1"> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + </button> + <div class="navbar-logo"> + <a href="/"> + <img alt="Apache Flink" src="/img/navbar-brand-logo.png" width="147px" height="73px"> + </a> + </div> + </div><!-- /.navbar-header --> + + <!-- The navigation links. --> + <div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1"> + <ul class="nav navbar-nav navbar-main"> + + <!-- Downloads --> + <li class=""><a class="btn btn-info" href="/downloads.html">Download Flink</a></li> + + <!-- Overview --> + <li><a href="/index.html">Home</a></li> + + <!-- Intro --> + <li><a href="/introduction.html">Introduction to Flink</a></li> + + <!-- Use cases --> + <li><a href="/usecases.html">Flink Use Cases</a></li> + + <!-- Powered by --> + <li><a href="/poweredby.html">Powered by Flink</a></li> + + <!-- Ecosystem --> + <li><a href="/ecosystem.html">Ecosystem</a></li> + + <!-- Community --> + <li><a href="/community.html">Community & Project Info</a></li> + + <!-- Contribute --> + <li><a href="/how-to-contribute.html">How to Contribute</a></li> + + <!-- Blog --> + <li class=" active hidden-md hidden-sm"><a href="/blog/"><b>Flink Blog</b></a></li> + + <hr /> + + + + <!-- Documentation --> + <!-- <li> + <a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1"; target="_blank">Documentation <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> --> + <li class="dropdown"> + <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation + <span class="caret"></span></a> + <ul class="dropdown-menu"> + <li><a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1"; target="_blank">1.1 (Latest stable release) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + <li><a href="http://ci.apache.org/projects/flink/flink-docs-release-1.2"; target="_blank">1.2 (Snapshot) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + </ul> + </li> + + <!-- Quickstart --> + <li> + <a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1/quickstart/setup_quickstart.html"; target="_blank">Quickstart <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> + + <!-- GitHub --> + <li> + <a href="https://github.com/apache/flink"; target="_blank">Flink on GitHub <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> + + + + + + + </ul> + + + + <ul class="nav navbar-nav navbar-bottom"> + <hr /> + + <!-- FAQ --> + <li ><a href="/faq.html">Project FAQ</a></li> + + <!-- Twitter --> + <li><a href="https://twitter.com/apacheflink"; target="_blank">@ApacheFlink <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + + <!-- Visualizer --> + <li class=" hidden-md hidden-sm"><a href="/visualizer/" target="_blank">Plan Visualizer <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + + </ul> + </div><!-- /.navbar-collapse --> + </nav> + + </div> + <div class="col-sm-9"> + <div class="row-fluid"> + <div class="col-sm-12"> + <div class="row"> + <h1>Peeking into Apache Flink's Engine Room</h1> + + <article> + <p>13 Mar 2015 by Fabian Hüske (<a href="https://twitter.com/fhueske";>@fhueske</a>)</p> + +<h3 id="join-processing-in-apache-flink">Join Processing in Apache Flink</h3> + +<p>Joins are prevalent operations in many data processing applications. Most data processing systems feature APIs that make joining data sets very easy. However, the internal algorithms for join processing are much more involved â especially if large data sets need to be efficiently handled. Therefore, join processing serves as a good example to discuss the salient design points and implementation details of a data processing system.</p> + +<p>In this blog post, we cut through Apache Flinkâs layered architecture and take a look at its internals with a focus on how it handles joins. Specifically, I will</p> + +<ul> + <li>show how easy it is to join data sets using Flinkâs fluent APIs,</li> + <li>discuss basic distributed join strategies, Flinkâs join implementations, and its memory management,</li> + <li>talk about Flinkâs optimizer that automatically chooses join strategies,</li> + <li>show some performance numbers for joining data sets of different sizes, and finally</li> + <li>briefly discuss joining of co-located and pre-sorted data sets.</li> +</ul> + +<p><em>Disclaimer</em>: This blog post is exclusively about equi-joins. Whenever I say âjoinâ in the following, I actually mean âequi-joinâ.</p> + +<h3 id="how-do-i-join-with-flink">How do I join with Flink?</h3> + +<p>Flink provides fluent APIs in Java and Scala to write data flow programs. Flinkâs APIs are centered around parallel data collections which are called data sets. data sets are processed by applying Transformations that compute new data sets. Flinkâs transformations include Map and Reduce as known from MapReduce <a href="http://research.google.com/archive/mapreduce.html";>[1]</a> but also operators for joining, co-grouping, and iterative processing. The documentation gives an overview of all available transformations <a href="http://ci.apache.org/projects/flink/flink-docs-release-0.8/dataset_transformations.html";>[2]</a>.</p> + +<p>Joining two Scala case class data sets is very easy as the following example shows:</p> + +<div class="highlight"><pre><code class="language-scala"><span class="c1">// define your data types</span> +<span class="k">case</span> <span class="k">class</span> <span class="nc">PageVisit</span><span class="o">(</span><span class="n">url</span><span class="k">:</span> <span class="kt">String</span><span class="o">,</span> <span class="n">ip</span><span class="k">:</span> <span class="kt">String</span><span class="o">,</span> <span class="n">userId</span><span class="k">:</span> <span class="kt">Long</span><span class="o">)</span> +<span class="k">case</span> <span class="k">class</span> <span class="nc">User</span><span class="o">(</span><span class="n">id</span><span class="k">:</span> <span class="kt">Long</span><span class="o">,</span> <span class="n">name</span><span class="k">:</span> <span class="kt">String</span><span class="o">,</span> <span class="n">email</span><span class="k">:</span> <span class="kt">String</span><span class="o">,</span> <span class="n">country</span><span class="k">:</span> <span class="kt">String</span><span class="o">)</span> + +<span class="c1">// get your data from somewhere</span> +<span class="k">val</span> <span class="n">visits</span><span class="k">:</span> <span class="kt">DataSet</span><span class="o">[</span><span class="kt">PageVisit</span><span class="o">]</span> <span class="k">=</span> <span class="o">...</span> +<span class="k">val</span> <span class="n">users</span><span class="k">:</span> <span class="kt">DataSet</span><span class="o">[</span><span class="kt">User</span><span class="o">]</span> <span class="k">=</span> <span class="o">...</span> + +<span class="c1">// filter the users data set</span> +<span class="k">val</span> <span class="n">germanUsers</span> <span class="k">=</span> <span class="n">users</span><span class="o">.</span><span class="n">filter</span><span class="o">((</span><span class="n">u</span><span class="o">)</span> <span class="k">=></span> <span class="n">u</span><span class="o">.</span><span class="n">country</span><span class="o">.</span><span class="n">equals</span><span class="o">(</span><span class="s">"de"</span><span class="o">))</span> +<span class="c1">// join data sets</span> +<span class="k">val</span> <span class="n">germanVisits</span><span class="k">:</span> <span class="kt">DataSet</span><span class="o">[(</span><span class="kt">PageVisit</span>, <span class="kt">User</span><span class="o">)]</span> <span class="k">=</span> + <span class="c1">// equi-join condition (PageVisit.userId = User.id)</span> + <span class="n">visits</span><span class="o">.</span><span class="n">join</span><span class="o">(</span><span class="n">germanUsers</span><span class="o">).</span><span class="n">where</span><span class="o">(</span><span class="s">"userId"</span><span class="o">).</span><span class="n">equalTo</span><span class="o">(</span><span class="s">"id"</span><span class="o">)</span></code></pre></div> + +<p>Flinkâs APIs also allow to:</p> + +<ul> + <li>apply a user-defined join function to each pair of joined elements instead returning a <code>($Left, $Right)</code> tuple,</li> + <li>select fields of pairs of joined Tuple elements (projection), and</li> + <li>define composite join keys such as <code>.where(âorderDateâ, âzipCodeâ).equalTo(âdateâ, âzipâ)</code>.</li> +</ul> + +<p>See the documentation for more details on Flinkâs join features <a href="http://ci.apache.org/projects/flink/flink-docs-release-0.8/dataset_transformations.html#join";>[3]</a>.</p> + +<h3 id="how-does-flink-join-my-data">How does Flink join my data?</h3> + +<p>Flink uses techniques which are well known from parallel database systems to efficiently execute parallel joins. A join operator must establish all pairs of elements from its input data sets for which the join condition evaluates to true. In a standalone system, the most straight-forward implementation of a join is the so-called nested-loop join which builds the full Cartesian product and evaluates the join condition for each pair of elements. This strategy has quadratic complexity and does obviously not scale to large inputs.</p> + +<p>In a distributed system joins are commonly processed in two steps:</p> + +<ol> + <li>The data of both inputs is distributed across all parallel instances that participate in the join and</li> + <li>each parallel instance performs a standard stand-alone join algorithm on its local partition of the overall data.</li> +</ol> + +<p>The distribution of data across parallel instances must ensure that each valid join pair can be locally built by exactly one instance. For both steps, there are multiple valid strategies that can be independently picked and which are favorable in different situations. In Flink terminology, the first phase is called Ship Strategy and the second phase Local Strategy. In the following I will describe Flinkâs ship and local strategies to join two data sets <em>R</em> and <em>S</em>.</p> + +<h4 id="ship-strategies">Ship Strategies</h4> +<p>Flink features two ship strategies to establish a valid data partitioning for a join:</p> + +<ul> + <li>the <em>Repartition-Repartition</em> strategy (RR) and</li> + <li>the <em>Broadcast-Forward</em> strategy (BF).</li> +</ul> + +<p>The Repartition-Repartition strategy partitions both inputs, R and S, on their join key attributes using the same partitioning function. Each partition is assigned to exactly one parallel join instance and all data of that partition is sent to its associated instance. This ensures that all elements that share the same join key are shipped to the same parallel instance and can be locally joined. The cost of the RR strategy is a full shuffle of both data sets over the network.</p> + +<center> +<img src="/img/blog/joins-repartition.png" style="width:90%;margin:15px" /> +</center> + +<p>The Broadcast-Forward strategy sends one complete data set (R) to each parallel instance that holds a partition of the other data set (S), i.e., each parallel instance receives the full data set R. Data set S remains local and is not shipped at all. The cost of the BF strategy depends on the size of R and the number of parallel instances it is shipped to. The size of S does not matter because S is not moved. The figure below illustrates how both ship strategies work.</p> + +<center> +<img src="/img/blog/joins-broadcast.png" style="width:90%;margin:15px" /> +</center> + +<p>The Repartition-Repartition and Broadcast-Forward ship strategies establish suitable data distributions to execute a distributed join. Depending on the operations that are applied before the join, one or even both inputs of a join are already distributed in a suitable way across parallel instances. In this case, Flink will reuse such distributions and only ship one or no input at all.</p> + +<h4 id="flinks-memory-management">Flinkâs Memory Management</h4> +<p>Before delving into the details of Flinkâs local join algorithms, I will briefly discuss Flinkâs internal memory management. Data processing algorithms such as joining, grouping, and sorting need to hold portions of their input data in memory. While such algorithms perform best if there is enough memory available to hold all data, it is crucial to gracefully handle situations where the data size exceeds memory. Such situations are especially tricky in JVM-based systems such as Flink because the system needs to reliably recognize that it is short on memory. Failure to detect such situations can result in an <code>OutOfMemoryException</code> and kill the JVM.</p> + +<p>Flink handles this challenge by actively managing its memory. When a worker node (TaskManager) is started, it allocates a fixed portion (70% by default) of the JVMâs heap memory that is available after initialization as 32KB byte arrays. These byte arrays are distributed as working memory to all algorithms that need to hold significant portions of data in memory. The algorithms receive their input data as Java data objects and serialize them into their working memory.</p> + +<p>This design has several nice properties. First, the number of data objects on the JVM heap is much lower resulting in less garbage collection pressure. Second, objects on the heap have a certain space overhead and the binary representation is more compact. Especially data sets of many small elements benefit from that. Third, an algorithm knows exactly when the input data exceeds its working memory and can react by writing some of its filled byte arrays to the workerâs local filesystem. After the content of a byte array is written to disk, it can be reused to process more data. Reading data back into memory is as simple as reading the binary data from the local filesystem. The following figure illustrates Flinkâs memory management.</p> + +<center> +<img src="/img/blog/joins-memmgmt.png" style="width:90%;margin:15px" /> +</center> + +<p>This active memory management makes Flink extremely robust for processing very large data sets on limited memory resources while preserving all benefits of in-memory processing if data is small enough to fit in-memory. De/serializing data into and from memory has a certain cost overhead compared to simply holding all data elements on the JVMâs heap. However, Flink features efficient custom de/serializers which also allow to perform certain operations such as comparisons directly on serialized data without deserializing data objects from memory.</p> + +<h4 id="local-strategies">Local Strategies</h4> + +<p>After the data has been distributed across all parallel join instances using either a Repartition-Repartition or Broadcast-Forward ship strategy, each instance runs a local join algorithm to join the elements of its local partition. Flinkâs runtime features two common join strategies to perform these local joins:</p> + +<ul> + <li>the <em>Sort-Merge-Join</em> strategy (SM) and</li> + <li>the <em>Hybrid-Hash-Join</em> strategy (HH).</li> +</ul> + +<p>The Sort-Merge-Join works by first sorting both input data sets on their join key attributes (Sort Phase) and merging the sorted data sets as a second step (Merge Phase). The sort is done in-memory if the local partition of a data set is small enough. Otherwise, an external merge-sort is done by collecting data until the working memory is filled, sorting it, writing the sorted data to the local filesystem, and starting over by filling the working memory again with more incoming data. After all input data has been received, sorted, and written as sorted runs to the local file system, a fully sorted stream can be obtained. This is done by reading the partially sorted runs from the local filesystem and sort-merging the records on the fly. Once the sorted streams of both inputs are available, both streams are sequentially read and merge-joined in a zig-zag fashion by comparing the sorted join key attributes, building join element pairs for matching keys, and advancing the sorted stre am with the lower join key. The figure below shows how the Sort-Merge-Join strategy works.</p> + +<center> +<img src="/img/blog/joins-smj.png" style="width:90%;margin:15px" /> +</center> + +<p>The Hybrid-Hash-Join distinguishes its inputs as build-side and probe-side input and works in two phases, a build phase followed by a probe phase. In the build phase, the algorithm reads the build-side input and inserts all data elements into an in-memory hash table indexed by their join key attributes. If the hash table outgrows the algorithmâs working memory, parts of the hash table (ranges of hash indexes) are written to the local filesystem. The build phase ends after the build-side input has been fully consumed. In the probe phase, the algorithm reads the probe-side input and probes the hash table for each element using its join key attribute. If the element falls into a hash index range that was spilled to disk, the element is also written to disk. Otherwise, the element is immediately joined with all matching elements from the hash table. If the hash table completely fits into the working memory, the join is finished after the probe-side input has been fully consumed. Ot herwise, the current hash table is dropped and a new hash table is built using spilled parts of the build-side input. This hash table is probed by the corresponding parts of the spilled probe-side input. Eventually, all data is joined. Hybrid-Hash-Joins perform best if the hash table completely fits into the working memory because an arbitrarily large the probe-side input can be processed on-the-fly without materializing it. However even if build-side input does not fit into memory, the the Hybrid-Hash-Join has very nice properties. In this case, in-memory processing is partially preserved and only a fraction of the build-side and probe-side data needs to be written to and read from the local filesystem. The next figure illustrates how the Hybrid-Hash-Join works.</p> + +<center> +<img src="/img/blog/joins-hhj.png" style="width:90%;margin:15px" /> +</center> + +<h3 id="how-does-flink-choose-join-strategies">How does Flink choose join strategies?</h3> + +<p>Ship and local strategies do not depend on each other and can be independently chosen. Therefore, Flink can execute a join of two data sets R and S in nine different ways by combining any of the three ship strategies (RR, BF with R being broadcasted, BF with S being broadcasted) with any of the three local strategies (SM, HH with R being build-side, HH with S being build-side). Each of these strategy combinations results in different execution performance depending on the data sizes and the available amount of working memory. In case of a small data set R and a much larger data set S, broadcasting R and using it as build-side input of a Hybrid-Hash-Join is usually a good choice because the much larger data set S is not shipped and not materialized (given that the hash table completely fits into memory). If both data sets are rather large or the join is performed on many parallel instances, repartitioning both inputs is a robust choice.</p> + +<p>Flink features a cost-based optimizer which automatically chooses the execution strategies for all operators including joins. Without going into the details of cost-based optimization, this is done by computing cost estimates for execution plans with different strategies and picking the plan with the least estimated costs. Thereby, the optimizer estimates the amount of data which is shipped over the the network and written to disk. If no reliable size estimates for the input data can be obtained, the optimizer falls back to robust default choices. A key feature of the optimizer is to reason about existing data properties. For example, if the data of one input is already partitioned in a suitable way, the generated candidate plans will not repartition this input. Hence, the choice of a RR ship strategy becomes more likely. The same applies for previously sorted data and the Sort-Merge-Join strategy. Flink programs can help the optimizer to reason about existing data properties by providing semantic information about user-defined functions <a href="https://ci.apache.org/projects/flink/flink-docs-release-1.0/apis/batch/index.html#semantic-annotations";>[4]</a>. While the optimizer is a killer feature of Flink, it can happen that a user knows better than the optimizer how to execute a specific join. Similar to relational database systems, Flink offers optimizer hints to tell the optimizer which join strategies to pick <a href="https://ci.apache.org/projects/flink/flink-docs-release-1.0/apis/batch/dataset_transformations.html#join-algorithm-hints";>[5]</a>.</p> + +<h3 id="how-is-flinks-join-performance">How is Flinkâs join performance?</h3> + +<p>Alright, that sounds good, but how fast are joins in Flink? Letâs have a look. We start with a benchmark of the single-core performance of Flinkâs Hybrid-Hash-Join implementation and run a Flink program that executes a Hybrid-Hash-Join with parallelism 1. We run the program on a n1-standard-2 Google Compute Engine instance (2 vCPUs, 7.5GB memory) with two locally attached SSDs. We give 4GB as working memory to the join. The join program generates 1KB records for both inputs on-the-fly, i.e., the data is not read from disk. We run 1:N (Primary-Key/Foreign-Key) joins and generate the smaller input with unique Integer join keys and the larger input with randomly chosen Integer join keys that fall into the key range of the smaller input. Hence, each tuple of the larger side joins with exactly one tuple of the smaller side. The result of the join is immediately discarded. We vary the size of the build-side input from 1 million to 12 million elements (1GB to 12GB). The probe-side i nput is kept constant at 64 million elements (64GB). The following chart shows the average execution time of three runs for each setup.</p> + +<center> +<img src="/img/blog/joins-single-perf.png" style="width:85%;margin:15px" /> +</center> + +<p>The joins with 1 to 3 GB build side (blue bars) are pure in-memory joins. The other joins partially spill data to disk (4 to 12GB, orange bars). The results show that the performance of Flinkâs Hybrid-Hash-Join remains stable as long as the hash table completely fits into memory. As soon as the hash table becomes larger than the working memory, parts of the hash table and corresponding parts of the probe side are spilled to disk. The chart shows that the performance of the Hybrid-Hash-Join gracefully decreases in this situation, i.e., there is no sharp increase in runtime when the join starts spilling. In combination with Flinkâs robust memory management, this execution behavior gives smooth performance without the need for fine-grained, data-dependent memory tuning.</p> + +<p>So, Flinkâs Hybrid-Hash-Join implementation performs well on a single thread even for limited memory resources, but how good is Flinkâs performance when joining larger data sets in a distributed setting? For the next experiment we compare the performance of the most common join strategy combinations, namely:</p> + +<ul> + <li>Broadcast-Forward, Hybrid-Hash-Join (broadcasting and building with the smaller side),</li> + <li>Repartition, Hybrid-Hash-Join (building with the smaller side), and</li> + <li>Repartition, Sort-Merge-Join</li> +</ul> + +<p>for different input size ratios:</p> + +<ul> + <li>1GB : 1000GB</li> + <li>10GB : 1000GB</li> + <li>100GB : 1000GB</li> + <li>1000GB : 1000GB</li> +</ul> + +<p>The Broadcast-Forward strategy is only executed for up to 10GB. Building a hash table from 100GB broadcasted data in 5GB working memory would result in spilling proximately 95GB (build input) + 950GB (probe input) in each parallel thread and require more than 8TB local disk storage on each machine.</p> + +<p>As in the single-core benchmark, we run 1:N joins, generate the data on-the-fly, and immediately discard the result after the join. We run the benchmark on 10 n1-highmem-8 Google Compute Engine instances. Each instance is equipped with 8 cores, 52GB RAM, 40GB of which are configured as working memory (5GB per core), and one local SSD for spilling to disk. All benchmarks are performed using the same configuration, i.e., no fine tuning for the respective data sizes is done. The programs are executed with a parallelism of 80.</p> + +<center> +<img src="/img/blog/joins-dist-perf.png" style="width:70%;margin:15px" /> +</center> + +<p>As expected, the Broadcast-Forward strategy performs best for very small inputs because the large probe side is not shipped over the network and is locally joined. However, when the size of the broadcasted side grows, two problems arise. First the amount of data which is shipped increases but also each parallel instance has to process the full broadcasted data set. The performance of both Repartitioning strategies behaves similar for growing input sizes which indicates that these strategies are mainly limited by the cost of the data transfer (at max 2TB are shipped over the network and joined). Although the Sort-Merge-Join strategy shows the worst performance all shown cases, it has a right to exist because it can nicely exploit sorted input data.</p> + +<h3 id="ive-got-sooo-much-data-to-join-do-i-really-need-to-ship-it">Iâve got sooo much data to join, do I really need to ship it?</h3> + +<p>We have seen that off-the-shelf distributed joins work really well in Flink. But what if your data is so huge that you do not want to shuffle it across your cluster? We recently added some features to Flink for specifying semantic properties (partitioning and sorting) on input splits and co-located reading of local input files. With these tools at hand, it is possible to join pre-partitioned data sets from your local filesystem without sending a single byte over your clusterâs network. If the input data is even pre-sorted, the join can be done as a Sort-Merge-Join without sorting, i.e., the join is essentially done on-the-fly. Exploiting co-location requires a very special setup though. Data needs to be stored on the local filesystem because HDFS does not feature data co-location and might move file blocks across data nodes. That means you need to take care of many things yourself which HDFS would have done for you, including replication to avoid data loss. On the other hand, p erformance gains of joining co-located and pre-sorted can be quite substantial.</p> + +<h3 id="tldr-what-should-i-remember-from-all-of-this">tl;dr: What should I remember from all of this?</h3> + +<ul> + <li>Flinkâs fluent Scala and Java APIs make joins and other data transformations easy as cake.</li> + <li>The optimizer does the hard choices for you, but gives you control in case you know better.</li> + <li>Flinkâs join implementations perform very good in-memory and gracefully degrade when going to disk.</li> + <li>Due to Flinkâs robust memory management, there is no need for job- or data-specific memory tuning to avoid a nasty <code>OutOfMemoryException</code>. It just runs out-of-the-box.</li> +</ul> + +<h4 id="references">References</h4> + +<p>[1] <a href="">âMapReduce: Simplified data processing on large clustersâ</a>, Dean, Ghemawat, 2004 <br /> +[2] <a href="http://ci.apache.org/projects/flink/flink-docs-release-0.8/dataset_transformations.html";>Flink 0.8.1 documentation: Data Transformations</a> <br /> +[3] <a href="http://ci.apache.org/projects/flink/flink-docs-release-0.8/dataset_transformations.html#join";>Flink 0.8.1 documentation: Joins</a> <br /> +[4] <a href="https://ci.apache.org/projects/flink/flink-docs-release-1.0/apis/batch/index.html#semantic-annotations";>Flink 1.0 documentation: Semantic annotations</a> <br /> +[5] <a href="https://ci.apache.org/projects/flink/flink-docs-release-1.0/apis/batch/dataset_transformations.html#join-algorithm-hints";>Flink 1.0 documentation: Optimizer join hints</a> <br /></p> + + </article> + </div> + + <div class="row"> + <div id="disqus_thread"></div> + <script type="text/javascript"> + /* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */ + var disqus_shortname = 'stratosphere-eu'; // required: replace example with your forum shortname + + /* * * DON'T EDIT BELOW THIS LINE * * */ + (function() { + var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true; + dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js'; + (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq); + })(); + </script> + </div> + </div> +</div> + </div> + </div> + + <hr /> + + <div class="row"> + <div class="footer text-center col-sm-12"> + <p>Copyright © 2014-2016 <a href="http://apache.org";>The Apache Software Foundation</a>. All Rights Reserved.</p> + <p>Apache Flink, Apache, and the Apache feather logo are either registered trademarks or trademarks of The Apache Software Foundation.</p> + <p><a href="/privacy-policy.html">Privacy Policy</a> · <a href="/blog/feed.xml">RSS feed</a></p> + </div> + </div> + </div><!-- /.container --> + + <!-- Include all compiled plugins (below), or include individual files as needed --> + <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js";></script> + <script src="/js/codetabs.js"></script> + <script src="/js/stickysidebar.js"></script> + + + <!-- Google Analytics --> + <script> + (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ + (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), + m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) + })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); + + ga('create', 'UA-52545728-1', 'auto'); + ga('send', 'pageview'); + </script> + </body> +</html> http://git-wip-us.apache.org/repos/asf/flink-web/blob/9ec0a879/content/news/2015/04/07/march-in-flink.html ---------------------------------------------------------------------- diff --git a/content/news/2015/04/07/march-in-flink.html b/content/news/2015/04/07/march-in-flink.html new file mode 100644 index 0000000..5a37e4d --- /dev/null +++ b/content/news/2015/04/07/march-in-flink.html @@ -0,0 +1,259 @@ +<!DOCTYPE html> +<html lang="en"> + <head> + <meta charset="utf-8"> + <meta http-equiv="X-UA-Compatible" content="IE=edge"> + <meta name="viewport" content="width=device-width, initial-scale=1"> + <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags --> + <title>Apache Flink: March 2015 in the Flink community</title> + <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon"> + <link rel="icon" href="/favicon.ico" type="image/x-icon"> + + <!-- Bootstrap --> + <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap.min.css";> + <link rel="stylesheet" href="/css/flink.css"> + <link rel="stylesheet" href="/css/syntax.css"> + + <!-- Blog RSS feed --> + <link href="/blog/feed.xml" rel="alternate" type="application/rss+xml" title="Apache Flink Blog: RSS feed" /> + + <!-- jQuery (necessary for Bootstrap's JavaScript plugins) --> + <!-- We need to load Jquery in the header for custom google analytics event tracking--> + <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.2/jquery.min.js";></script> + + <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries --> + <!-- WARNING: Respond.js doesn't work if you view the page via file:// --> + <!--[if lt IE 9]> + <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js";></script> + <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js";></script> + <![endif]--> + </head> + <body> + + + <!-- Main content. --> + <div class="container"> + <div class="row"> + + + <div id="sidebar" class="col-sm-3"> + <!-- Top navbar. --> + <nav class="navbar navbar-default"> + <!-- The logo. --> + <div class="navbar-header"> + <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1"> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + </button> + <div class="navbar-logo"> + <a href="/"> + <img alt="Apache Flink" src="/img/navbar-brand-logo.png" width="147px" height="73px"> + </a> + </div> + </div><!-- /.navbar-header --> + + <!-- The navigation links. --> + <div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1"> + <ul class="nav navbar-nav navbar-main"> + + <!-- Downloads --> + <li class=""><a class="btn btn-info" href="/downloads.html">Download Flink</a></li> + + <!-- Overview --> + <li><a href="/index.html">Home</a></li> + + <!-- Intro --> + <li><a href="/introduction.html">Introduction to Flink</a></li> + + <!-- Use cases --> + <li><a href="/usecases.html">Flink Use Cases</a></li> + + <!-- Powered by --> + <li><a href="/poweredby.html">Powered by Flink</a></li> + + <!-- Ecosystem --> + <li><a href="/ecosystem.html">Ecosystem</a></li> + + <!-- Community --> + <li><a href="/community.html">Community & Project Info</a></li> + + <!-- Contribute --> + <li><a href="/how-to-contribute.html">How to Contribute</a></li> + + <!-- Blog --> + <li class=" active hidden-md hidden-sm"><a href="/blog/"><b>Flink Blog</b></a></li> + + <hr /> + + + + <!-- Documentation --> + <!-- <li> + <a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1"; target="_blank">Documentation <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> --> + <li class="dropdown"> + <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation + <span class="caret"></span></a> + <ul class="dropdown-menu"> + <li><a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1"; target="_blank">1.1 (Latest stable release) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + <li><a href="http://ci.apache.org/projects/flink/flink-docs-release-1.2"; target="_blank">1.2 (Snapshot) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + </ul> + </li> + + <!-- Quickstart --> + <li> + <a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1/quickstart/setup_quickstart.html"; target="_blank">Quickstart <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> + + <!-- GitHub --> + <li> + <a href="https://github.com/apache/flink"; target="_blank">Flink on GitHub <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> + + + + + + + </ul> + + + + <ul class="nav navbar-nav navbar-bottom"> + <hr /> + + <!-- FAQ --> + <li ><a href="/faq.html">Project FAQ</a></li> + + <!-- Twitter --> + <li><a href="https://twitter.com/apacheflink"; target="_blank">@ApacheFlink <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + + <!-- Visualizer --> + <li class=" hidden-md hidden-sm"><a href="/visualizer/" target="_blank">Plan Visualizer <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + + </ul> + </div><!-- /.navbar-collapse --> + </nav> + + </div> + <div class="col-sm-9"> + <div class="row-fluid"> + <div class="col-sm-12"> + <div class="row"> + <h1>March 2015 in the Flink community</h1> + + <article> + <p>07 Apr 2015</p> + +<p>March has been a busy month in the Flink community.</p> + +<h3 id="scaling-als">Scaling ALS</h3> + +<p>Flink committers employed at <a href="http://data-artisans.com";>data Artisans</a> published a <a href="http://data-artisans.com/how-to-factorize-a-700-gb-matrix-with-apache-flink/";>blog post</a> on how they scaled matrix factorization with Flink and Google Compute Engine to matrices with 28 billion elements.</p> + +<h3 id="learn-about-the-internals-of-flink">Learn about the internals of Flink</h3> + +<p>The community has started an effort to better document the internals +of Flink. Check out the first articles on the Flink wiki on <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=53741525";>how Flink +manages +memory</a>, +<a href="https://cwiki.apache.org/confluence/display/FLINK/Data+exchange+between+tasks";>how tasks in Flink exchange +data</a>, +<a href="https://cwiki.apache.org/confluence/display/FLINK/Type+System%2C+Type+Extraction%2C+Serialization";>type extraction and serialization in +Flink</a>, +as well as <a href="https://cwiki.apache.org/confluence/display/FLINK/Akka+and+Actors";>how Flink builds on Akka for distributed +coordination</a>.</p> + +<p>Check out also the <a href="http://flink.apache.org/news/2015/03/13/peeking-into-Apache-Flinks-Engine-Room.html";>new blog +post</a> +on how Flink executes joins with several insights into Flinkâs runtime.</p> + +<h3 id="meetups-and-talks">Meetups and talks</h3> + +<p>Flinkâs machine learning efforts were presented at the <a href="http://www.meetup.com/Machine-Learning-Stockholm/events/221144997/";>Machine +Learning Stockholm meetup +group</a>. The +regular Berlin Flink meetup featured a talk on the past, present, and +future of Flink. The talk is available on +<a href="https://www.youtube.com/watch?v=fw2DBE6ZiEQ&feature=youtu.be";>youtube</a>.</p> + +<h2 id="in-the-flink-master">In the Flink master</h2> + +<h3 id="table-api-in-scala-and-java">Table API in Scala and Java</h3> + +<p>The new <a href="https://github.com/apache/flink/tree/master/flink-libraries/flink-table";>Table +API</a> +in Flink is now available in both Java and Scala. Check out the +examples <a href="https://github.com/apache/flink/blob/master/flink-libraries/flink-table/src/main/java/org/apache/flink/examples/java/JavaTableExample.java";>here (Java)</a> and <a href="https://github.com/apache/flink/tree/master/flink-libraries/flink-table/src/main/scala/org/apache/flink/examples/scala";>here (Scala)</a>.</p> + +<h3 id="additions-to-the-machine-learning-library">Additions to the Machine Learning library</h3> + +<p>Flinkâs <a href="https://github.com/apache/flink/tree/master/flink-libraries/flink-ml";>Machine Learning +library</a> +is seeing quite a bit of traction. Recent additions include the <a href="http://arxiv.org/abs/1409.1458";>CoCoA +algorithm</a> for distributed +optimization.</p> + +<h3 id="exactly-once-delivery-guarantees-for-streaming-jobs">Exactly-once delivery guarantees for streaming jobs</h3> + +<p>Flink streaming jobs now provide exactly once processing guarantees +when coupled with persistent sources (notably <a href="http://kafka.apache.org";>Apache +Kafka</a>). Flink periodically checkpoints and +persists the offsets of the sources and restarts from those +checkpoints at failure recovery. This functionality is currently +limited in that it does not yet handle large state and iterative +programs.</p> + + + </article> + </div> + + <div class="row"> + <div id="disqus_thread"></div> + <script type="text/javascript"> + /* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */ + var disqus_shortname = 'stratosphere-eu'; // required: replace example with your forum shortname + + /* * * DON'T EDIT BELOW THIS LINE * * */ + (function() { + var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true; + dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js'; + (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq); + })(); + </script> + </div> + </div> +</div> + </div> + </div> + + <hr /> + + <div class="row"> + <div class="footer text-center col-sm-12"> + <p>Copyright © 2014-2016 <a href="http://apache.org";>The Apache Software Foundation</a>. All Rights Reserved.</p> + <p>Apache Flink, Apache, and the Apache feather logo are either registered trademarks or trademarks of The Apache Software Foundation.</p> + <p><a href="/privacy-policy.html">Privacy Policy</a> · <a href="/blog/feed.xml">RSS feed</a></p> + </div> + </div> + </div><!-- /.container --> + + <!-- Include all compiled plugins (below), or include individual files as needed --> + <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js";></script> + <script src="/js/codetabs.js"></script> + <script src="/js/stickysidebar.js"></script> + + + <!-- Google Analytics --> + <script> + (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ + (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), + m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) + })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); + + ga('create', 'UA-52545728-1', 'auto'); + ga('send', 'pageview'); + </script> + </body> +</html> http://git-wip-us.apache.org/repos/asf/flink-web/blob/9ec0a879/content/news/2015/04/13/release-0.9.0-milestone1.html ---------------------------------------------------------------------- diff --git a/content/news/2015/04/13/release-0.9.0-milestone1.html b/content/news/2015/04/13/release-0.9.0-milestone1.html new file mode 100644 index 0000000..4e09ad3 --- /dev/null +++ b/content/news/2015/04/13/release-0.9.0-milestone1.html @@ -0,0 +1,444 @@ +<!DOCTYPE html> +<html lang="en"> + <head> + <meta charset="utf-8"> + <meta http-equiv="X-UA-Compatible" content="IE=edge"> + <meta name="viewport" content="width=device-width, initial-scale=1"> + <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags --> + <title>Apache Flink: Announcing Flink 0.9.0-milestone1 preview release</title> + <link rel="shortcut icon" href="/favicon.ico" type="image/x-icon"> + <link rel="icon" href="/favicon.ico" type="image/x-icon"> + + <!-- Bootstrap --> + <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap.min.css";> + <link rel="stylesheet" href="/css/flink.css"> + <link rel="stylesheet" href="/css/syntax.css"> + + <!-- Blog RSS feed --> + <link href="/blog/feed.xml" rel="alternate" type="application/rss+xml" title="Apache Flink Blog: RSS feed" /> + + <!-- jQuery (necessary for Bootstrap's JavaScript plugins) --> + <!-- We need to load Jquery in the header for custom google analytics event tracking--> + <script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.2/jquery.min.js";></script> + + <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries --> + <!-- WARNING: Respond.js doesn't work if you view the page via file:// --> + <!--[if lt IE 9]> + <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js";></script> + <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js";></script> + <![endif]--> + </head> + <body> + + + <!-- Main content. --> + <div class="container"> + <div class="row"> + + + <div id="sidebar" class="col-sm-3"> + <!-- Top navbar. --> + <nav class="navbar navbar-default"> + <!-- The logo. --> + <div class="navbar-header"> + <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1"> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + <span class="icon-bar"></span> + </button> + <div class="navbar-logo"> + <a href="/"> + <img alt="Apache Flink" src="/img/navbar-brand-logo.png" width="147px" height="73px"> + </a> + </div> + </div><!-- /.navbar-header --> + + <!-- The navigation links. --> + <div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1"> + <ul class="nav navbar-nav navbar-main"> + + <!-- Downloads --> + <li class=""><a class="btn btn-info" href="/downloads.html">Download Flink</a></li> + + <!-- Overview --> + <li><a href="/index.html">Home</a></li> + + <!-- Intro --> + <li><a href="/introduction.html">Introduction to Flink</a></li> + + <!-- Use cases --> + <li><a href="/usecases.html">Flink Use Cases</a></li> + + <!-- Powered by --> + <li><a href="/poweredby.html">Powered by Flink</a></li> + + <!-- Ecosystem --> + <li><a href="/ecosystem.html">Ecosystem</a></li> + + <!-- Community --> + <li><a href="/community.html">Community & Project Info</a></li> + + <!-- Contribute --> + <li><a href="/how-to-contribute.html">How to Contribute</a></li> + + <!-- Blog --> + <li class=" active hidden-md hidden-sm"><a href="/blog/"><b>Flink Blog</b></a></li> + + <hr /> + + + + <!-- Documentation --> + <!-- <li> + <a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1"; target="_blank">Documentation <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> --> + <li class="dropdown"> + <a class="dropdown-toggle" data-toggle="dropdown" href="#">Documentation + <span class="caret"></span></a> + <ul class="dropdown-menu"> + <li><a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1"; target="_blank">1.1 (Latest stable release) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + <li><a href="http://ci.apache.org/projects/flink/flink-docs-release-1.2"; target="_blank">1.2 (Snapshot) <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + </ul> + </li> + + <!-- Quickstart --> + <li> + <a href="http://ci.apache.org/projects/flink/flink-docs-release-1.1/quickstart/setup_quickstart.html"; target="_blank">Quickstart <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> + + <!-- GitHub --> + <li> + <a href="https://github.com/apache/flink"; target="_blank">Flink on GitHub <small><span class="glyphicon glyphicon-new-window"></span></small></a> + </li> + + + + + + + </ul> + + + + <ul class="nav navbar-nav navbar-bottom"> + <hr /> + + <!-- FAQ --> + <li ><a href="/faq.html">Project FAQ</a></li> + + <!-- Twitter --> + <li><a href="https://twitter.com/apacheflink"; target="_blank">@ApacheFlink <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + + <!-- Visualizer --> + <li class=" hidden-md hidden-sm"><a href="/visualizer/" target="_blank">Plan Visualizer <small><span class="glyphicon glyphicon-new-window"></span></small></a></li> + + </ul> + </div><!-- /.navbar-collapse --> + </nav> + + </div> + <div class="col-sm-9"> + <div class="row-fluid"> + <div class="col-sm-12"> + <div class="row"> + <h1>Announcing Flink 0.9.0-milestone1 preview release</h1> + + <article> + <p>13 Apr 2015</p> + +<p>The Apache Flink community is pleased to announce the availability of +the 0.9.0-milestone-1 release. The release is a preview of the +upcoming 0.9.0 release. It contains many new features which will be +available in the upcoming 0.9 release. Interested users are encouraged +to try it out and give feedback. As the version number indicates, this +release is a preview release that contains known issues.</p> + +<p>You can download the release +<a href="http://flink.apache.org/downloads.html#preview";>here</a> and check out the +latest documentation +<a href="http://ci.apache.org/projects/flink/flink-docs-master/";>here</a>. Feedback +through the Flink <a href="http://flink.apache.org/community.html#mailing-lists";>mailing +lists</a> is, as +always, very welcome!</p> + +<h2 id="new-features">New Features</h2> + +<h3 id="table-api">Table API</h3> + +<p>Flinkâs new Table API offers a higher-level abstraction for +interacting with structured data sources. The Table API allows users +to execute logical, SQL-like queries on distributed data sets while +allowing them to freely mix declarative queries with regular Flink +operators. Here is an example that groups and joins two tables:</p> + +<div class="highlight"><pre><code class="language-scala"><span class="k">val</span> <span class="n">clickCounts</span> <span class="k">=</span> <span class="n">clicks</span> + <span class="o">.</span><span class="n">groupBy</span><span class="o">(</span><span class="-Symbol">'user</span><span class="o">).</span><span class="n">select</span><span class="o">(</span><span class="-Symbol">'userId</span><span class="o">,</span> <span class="-Symbol">'url</span><span class="o">.</span><span class="n">count</span> <span class="n">as</span> <span class="-Symbol">'count</span><span class="o">)</span> + +<span class="k">val</span> <span class="n">activeUsers</span> <span class="k">=</span> <span class="n">users</span><span class="o">.</span><span class="n">join</span><span class="o">(</span><span class="n">clickCounts</span><span class="o">)</span> + <span class="o">.</span><span class="n">where</span><span class="o">(</span><span class="-Symbol">'id</span> <span class="o">===</span> <span class="-Symbol">'userId</span> <span class="o">&&</span> <span class="-Symbol">'count</span> <span class="o">></span> <span class="mi">10</span><span class="o">).</span><span class="n">select</span><span class="o">(</span><span class="-Symbol">'username</span><span class="o">,</span> <span class="-Symbol">'count</span><span class="o">,</span> <span class="o">...)</span></code></pre></div> + +<p>Tables consist of logical attributes that can be selected by name +rather than physical Java and Scala data types. This alleviates a lot +of boilerplate code for common ETL tasks and raises the abstraction +for Flink programs. Tables are available for both static and streaming +data sources (DataSet and DataStream APIs).</p> + +<p>Check out the Table guide for Java and Scala +<a href="https://ci.apache.org/projects/flink/flink-docs-master/apis/batch/libs/table.html";>here</a>.</p> + +<h3 id="gelly-graph-processing-api">Gelly Graph Processing API</h3> + +<p>Gelly is a Java Graph API for Flink. It contains a set of utilities +for graph analysis, support for iterative graph processing and a +library of graph algorithms. Gelly exposes a Graph data structure that +wraps DataSets for vertices and edges, as well as methods for creating +graphs from DataSets, graph transformations and utilities (e.g., in- +and out- degrees of vertices), neighborhood aggregations, iterative +vertex-centric graph processing, as well as a library of common graph +algorithms, including PageRank, SSSP, label propagation, and community +detection.</p> + +<p>Gelly internally builds on top of Flinkâs <a href="https://ci.apache.org/projects/flink/flink-docs-master/apis/batch/iterations.html";>delta +iterations</a>. Iterative +graph algorithms are executed leveraging mutable state, achieving +similar performance with specialized graph processing systems.</p> + +<p>Gelly will eventually subsume Spargel, Flinkâs Pregel-like API. Check +out the Gelly guide +<a href="https://ci.apache.org/projects/flink/flink-docs-master/apis/batch/libs/gelly.html";>here</a>.</p> + +<h3 id="flink-machine-learning-library">Flink Machine Learning Library</h3> + +<p>This release includes the first version of Flinkâs Machine Learning +library. The libraryâs pipeline approach, which has been strongly +inspired by scikit-learnâs abstraction of transformers and estimators, +makes it easy to quickly set up a data processing pipeline and to get +your job done.</p> + +<p>Flink distinguishes between transformers and learners. Transformers +are components which transform your input data into a new format +allowing you to extract features, cleanse your data or to sample from +it. Learners on the other hand constitute the components which take +your input data and train a model on it. The model you obtain from the +learner can then be evaluated and used to make predictions on unseen +data.</p> + +<p>Currently, the machine learning library contains transformers and +learners to do multiple tasks. The library supports multiple linear +regression using a stochastic gradient implementation to scale to +large data sizes. Furthermore, it includes an alternating least +squares (ALS) implementation to factorizes large matrices. The matrix +factorization can be used to do collaborative filtering. An +implementation of the communication efficient distributed dual +coordinate ascent (CoCoA) algorithm is the latest addition to the +library. The CoCoA algorithm can be used to train distributed +soft-margin SVMs.</p> + +<h3 id="flink-on-yarn-leveraging-apache-tez">Flink on YARN leveraging Apache Tez</h3> + +<p>We are introducing a new execution mode for Flink to be able to run +restricted Flink programs on top of <a href="http://tez.apache.org";>Apache +Tez</a>. This mode retains Flinkâs APIs, +optimizer, as well as Flinkâs runtime operators, but instead of +wrapping those in Flink tasks that are executed by Flink TaskManagers, +it wraps them in Tez runtime tasks and builds a Tez DAG that +represents the program.</p> + +<p>By using Flink on Tez, users have an additional choice for an +execution platform for Flink programs. While Flinkâs distributed +runtime favors low latency, streaming shuffles, and iterative +algorithms, Tez focuses on scalability and elastic resource usage in +shared YARN clusters.</p> + +<p>Get started with Flink on Tez +<a href="http://ci.apache.org/projects/flink/flink-docs-master/setup/flink_on_tez.html";>here</a>.</p> + +<h3 id="reworked-distributed-runtime-on-akka">Reworked Distributed Runtime on Akka</h3> + +<p>Flinkâs RPC system has been replaced by the widely adopted +<a href="http://akka.io";>Akka</a> framework. Akkaâs concurrency model offers the +right abstraction to develop a fast as well as robust distributed +system. By using Akkaâs own failure detection mechanism the stability +of Flinkâs runtime is significantly improved, because the system can +now react in proper form to node outages. Furthermore, Akka improves +Flinkâs scalability by introducing asynchronous messages to the +system. These asynchronous messages allow Flink to be run on many more +nodes than before.</p> + +<h3 id="exactly-once-processing-on-kafka-streaming-sources">Exactly-once processing on Kafka Streaming Sources</h3> + +<p>This release introduces stream processing with exacly-once delivery +guarantees for Flink streaming programs that analyze streaming sources +that are persisted by <a href="http://kafka.apache.org";>Apache Kafka</a>. The +system is internally tracking the Kafka offsets to ensure that Flink +can pick up data from Kafka where it left off in case of an failure.</p> + +<p>Read +<a href="http://ci.apache.org/projects/flink/flink-docs-master/apis/streaming_guide.html#apache-kafka";>here</a> +on how to use the persistent Kafka source.</p> + +<h3 id="improved-yarn-support">Improved YARN support</h3> + +<p>Flinkâs YARN client contains several improvements, such as a detached +mode for starting a YARN session in the background, the ability to +submit a single Flink job to a YARN cluster without starting a +session, including a âfire and forgetâ mode. Flink is now also able to +reallocate failed YARN containers to maintain the size of the +requested cluster. This feature allows to implement fault-tolerant +setups on top of YARN. There is also an internal Java API to deploy +and control a running YARN cluster. This is being used by system +integrators to easily control Flink on YARN within their Hadoop 2 +cluster.</p> + +<p>See the YARN docs +<a href="http://ci.apache.org/projects/flink/flink-docs-master/setup/yarn_setup.html";>here</a>.</p> + +<h2 id="more-improvements-and-fixes">More Improvements and Fixes</h2> + +<ul> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1605";>FLINK-1605</a>: +Flink is not exposing its Guava and ASM dependencies to Maven +projects depending on Flink. We use the maven-shade-plugin to +relocate these dependencies into our own namespace. This allows +users to use any Guava or ASM version.</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1605";>FLINK-1417</a>: +Automatic recognition and registration of Java Types at Kryo and the +internal serializers: Flink has its own type handling and +serialization framework falling back to Kryo for types that it cannot +handle. To get the best performance Flink is automatically registering +all types a user is using in their program with Kryo.Flink also +registers serializers for Protocol Buffers, Thrift, Avro and YodaTime +automatically. Users can also manually register serializers to Kryo +(https://issues.apache.org/jira/browse/FLINK-1399)</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1296";>FLINK-1296</a>: Add +support for sorting very large records</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1679";>FLINK-1679</a>: +âdegreeOfParallelismâ methods renamed to âparallelismâ</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1501";>FLINK-1501</a>: Add +metrics library for monitoring TaskManagers</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1760";>FLINK-1760</a>: Add +support for building Flink with Scala 2.11</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1648";>FLINK-1648</a>: Add +a mode where the system automatically sets the parallelism to the +available task slots</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1622";>FLINK-1622</a>: Add +groupCombine operator</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1589";>FLINK-1589</a>: Add +option to pass Configuration to LocalExecutor</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1504";>FLINK-1504</a>: Add +support for accessing secured HDFS clusters in standalone mode</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1478";>FLINK-1478</a>: Add +strictly local input split assignment</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1512";>FLINK-1512</a>: Add +CsvReader for reading into POJOs.</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1461";>FLINK-1461</a>: Add +sortPartition operator</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1450";>FLINK-1450</a>: Add +Fold operator to the Streaming api</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1389";>FLINK-1389</a>: +Allow setting custom file extensions for files created by the +FileOutputFormat</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1236";>FLINK-1236</a>: Add +support for localization of Hadoop Input Splits</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1179";>FLINK-1179</a>: Add +button to JobManager web interface to request stack trace of a +TaskManager</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1105";>FLINK-1105</a>: Add +support for locally sorted output</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1688";>FLINK-1688</a>: Add +socket sink</p> + </li> + <li> + <p><a href="https://issues.apache.org/jira/browse/FLINK-1436";>FLINK-1436</a>: +Improve usability of command line interface</p> + </li> +</ul> + + </article> + </div> + + <div class="row"> + <div id="disqus_thread"></div> + <script type="text/javascript"> + /* * * CONFIGURATION VARIABLES: EDIT BEFORE PASTING INTO YOUR WEBPAGE * * */ + var disqus_shortname = 'stratosphere-eu'; // required: replace example with your forum shortname + + /* * * DON'T EDIT BELOW THIS LINE * * */ + (function() { + var dsq = document.createElement('script'); dsq.type = 'text/javascript'; dsq.async = true; + dsq.src = '//' + disqus_shortname + '.disqus.com/embed.js'; + (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(dsq); + })(); + </script> + </div> + </div> +</div> + </div> + </div> + + <hr /> + + <div class="row"> + <div class="footer text-center col-sm-12"> + <p>Copyright © 2014-2016 <a href="http://apache.org";>The Apache Software Foundation</a>. All Rights Reserved.</p> + <p>Apache Flink, Apache, and the Apache feather logo are either registered trademarks or trademarks of The Apache Software Foundation.</p> + <p><a href="/privacy-policy.html">Privacy Policy</a> · <a href="/blog/feed.xml">RSS feed</a></p> + </div> + </div> + </div><!-- /.container --> + + <!-- Include all compiled plugins (below), or include individual files as needed --> + <script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/js/bootstrap.min.js";></script> + <script src="/js/codetabs.js"></script> + <script src="/js/stickysidebar.js"></script> + + + <!-- Google Analytics --> + <script> + (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ + (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), + m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) + })(window,document,'script','//www.google-analytics.com/analytics.js','ga'); + + ga('create', 'UA-52545728-1', 'auto'); + ga('send', 'pageview'); + </script> + </body> +</html>
