beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@apache.org
Subject [1/3] beam-site git commit: Clarify maturity of various runners.
Date Sat, 28 Jan 2017 18:25:04 GMT
Repository: beam-site
Updated Branches:
  refs/heads/asf-site 6df417f99 -> f1d931ea9


Clarify maturity of various runners.

Project: http://git-wip-us.apache.org/repos/asf/beam-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/beam-site/commit/65dbaab7
Tree: http://git-wip-us.apache.org/repos/asf/beam-site/tree/65dbaab7
Diff: http://git-wip-us.apache.org/repos/asf/beam-site/diff/65dbaab7

Branch: refs/heads/asf-site
Commit: 65dbaab75eb9ff1a3509af2dd63de61965c5cfb1
Parents: 6df417f
Author: Robert Bradshaw <robertwb@gmail.com>
Authored: Fri Jan 27 12:14:03 2017 -0800
Committer: Davor Bonaci <davor@google.com>
Committed: Sat Jan 28 10:23:03 2017 -0800

----------------------------------------------------------------------
 src/get-started/beam-overview.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/beam-site/blob/65dbaab7/src/get-started/beam-overview.md
----------------------------------------------------------------------
diff --git a/src/get-started/beam-overview.md b/src/get-started/beam-overview.md
index 6756a50..79716a9 100644
--- a/src/get-started/beam-overview.md
+++ b/src/get-started/beam-overview.md
@@ -40,7 +40,7 @@ Beam currently supports the following language-specific SDKs:
 
 ## Apache Beam Pipeline Runners
 
-The Beam Pipeline Runners translate the data processing pipeline you define with your Beam
program into the API compatible with the distributed processing back-end of your choice. When
you run your Beam program, you'll need to specify the appropriate runner for the back-end
where you want to execute your pipeline.
+The Beam Pipeline Runners translate the data processing pipeline you define with your Beam
program into the API compatible with the distributed processing back-end of your choice. When
you run your Beam program, you'll need to specify an [appropriate runner]({{ site.baseurl
}}/documentation/runners/capability-matrix) for the back-end where you want to execute your
pipeline.
 
 Beam currently supports Runners that work with the following distributed processing back-ends:
 
@@ -51,19 +51,19 @@ Beam currently supports Runners that work with the following distributed
process
 </tr>
 <tr>
   <td>Apache Apex</td>
-  <td>In Development</td>
+  <td>Active Development</td>
 </tr>
 <tr>
   <td>Apache Flink</td>
-  <td>In Development</td>
+  <td>Active Development</td>
 </tr>
 <tr>
   <td>Apache Spark</td>
-  <td>In Development</td>
+  <td>Active Development</td>
 </tr>
 <tr>
   <td>Google Cloud Dataflow</td>
-  <td>In Development</td>
+  <td>Active Development</td>
 </tr>
 </table>
 


Mime
View raw message