From 42c7110305273245c67473300c963178d368e6cd Mon Sep 17 00:00:00 2001 From: Maximilian Michels Date: Mon, 7 Mar 2016 11:54:28 +0100 Subject: [PATCH 1/2] [docs] update README Runner section --- README.md | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index db4a13fc8925..d942e2bba2b6 100644 --- a/README.md +++ b/README.md @@ -44,11 +44,15 @@ Have ideas for new SDKs or DSLs? See the [Jira](https://issues.apache.org/jira/b ### Runners -Beam supports executing programs on multiple distributed processing backends. After the Beam project's initial bootstrapping completes, it will include: - 1. The `DirectPipelineRunner` runs the pipeline on your local machine. - 2. The `DataflowPipelineRunner` submits the pipeline to the [Google Cloud Dataflow](http://cloud.google.com/dataflow/). - 3. The `SparkPipelineRunner` runs the pipeline on an Apache Spark cluster. See the code that will be donated at [cloudera/spark-dataflow](https://github.com/cloudera/spark-dataflow). - 4. The `FlinkPipelineRunner` runs the pipeline on an Apache Flink cluster. See the code that will be donated at [dataArtisans/flink-dataflow](https://github.com/dataArtisans/flink-dataflow). +Beam supports executing programs on multiple distributed processing backends (runners). It currently includes the following Runners: + +- The `DirectPipelineRunner` runs the pipeline on your local machine. +- The `DataflowPipelineRunner` submits the pipeline to the [Google Cloud Dataflow](http://cloud.google.com/dataflow/). +- The `FlinkPipelineRunner` runs the pipeline on an Apache Flink cluster. The code has been donated from [dataArtisans/flink-dataflow](https://github.com/dataArtisans/flink-dataflow) and is now part of Beam. + +After the Beam project's initial bootstrapping completes, it will include: +- The `SparkPipelineRunner` runs the pipeline on an Apache Spark cluster. See the code that will be donated at [cloudera/spark-dataflow](https://github.com/cloudera/spark-dataflow). +- The `GearpumpRunner` runs the pipeline on a Gearpump: [Gearpump](https://github.com/gearpump/gearpump) Have ideas for new Runners? See the [Jira](https://issues.apache.org/jira/browse/BEAM/component/12328916/). @@ -57,6 +61,10 @@ Have ideas for new Runners? See the [Jira](https://issues.apache.org/jira/browse _Coming soon!_ +### Flink Runner + +See the Flink Runner [README](https://github.com/apache/incubator-beam/runners/flink). + ## Contact Us From 9c6f2a776ac3b0c99cf38cf7e8093da9a3059161 Mon Sep 17 00:00:00 2001 From: Maximilian Michels Date: Tue, 8 Mar 2016 15:03:47 +0100 Subject: [PATCH 2/2] include suggestions --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index d942e2bba2b6..6dd4bccd8732 100644 --- a/README.md +++ b/README.md @@ -44,7 +44,7 @@ Have ideas for new SDKs or DSLs? See the [Jira](https://issues.apache.org/jira/b ### Runners -Beam supports executing programs on multiple distributed processing backends (runners). It currently includes the following Runners: +Beam supports executing programs on multiple distributed processing backends through PipelineRunners. Currently, the following PipelineRunners are available: - The `DirectPipelineRunner` runs the pipeline on your local machine. - The `DataflowPipelineRunner` submits the pipeline to the [Google Cloud Dataflow](http://cloud.google.com/dataflow/). @@ -52,7 +52,6 @@ Beam supports executing programs on multiple distributed processing backends (ru After the Beam project's initial bootstrapping completes, it will include: - The `SparkPipelineRunner` runs the pipeline on an Apache Spark cluster. See the code that will be donated at [cloudera/spark-dataflow](https://github.com/cloudera/spark-dataflow). -- The `GearpumpRunner` runs the pipeline on a Gearpump: [Gearpump](https://github.com/gearpump/gearpump) Have ideas for new Runners? See the [Jira](https://issues.apache.org/jira/browse/BEAM/component/12328916/).