commit | 324f0b3e3c618e724b211eca779546b61e97317a | [log] [tgz] |
---|---|---|
author | Charles Chen <charlesccychen@users.noreply.github.com> | Fri Oct 05 19:11:22 2018 -0400 |
committer | GitHub <noreply@github.com> | Fri Oct 05 19:11:22 2018 -0400 |
tree | 35417b81b1ffc5b366e4240c00fea5f493f43c0d | |
parent | e4965ad2590ec3b25b0de613399cbec88403afdc [diff] | |
parent | 7ed8f700adf0b8b8ac497a08b4eece69c311ebd4 [diff] |
Merge pull request #6564 from udim/pubsub-0-35-4 [BEAM-5513] Upgrade Python SDK to PubSub 0.35.4
Apache Beam is a unified model for defining both batch and streaming data-parallel processing pipelines, as well as a set of language-specific SDKs for constructing pipelines and Runners for executing them on distributed processing backends, including Apache Apex, Apache Flink, Apache Spark, and Google Cloud Dataflow.
Lang | SDK | Apex | Dataflow | Flink | Gearpump | Samza | Spark |
---|---|---|---|---|---|---|---|
Go | --- | --- | --- | --- | --- | --- | |
Java | |||||||
Python | --- | --- | --- | --- |
Beam provides a general approach to expressing embarrassingly parallel data processing pipelines and supports three categories of users, each of which have relatively disparate backgrounds and needs.
The model behind Beam evolved from a number of internal Google data processing projects, including MapReduce, FlumeJava, and Millwheel. This model was originally known as the “Dataflow Model”.
To learn more about the Beam Model (though still under the original name of Dataflow), see the World Beyond Batch: Streaming 101 and Streaming 102 posts on O’Reilly’s Radar site, and the VLDB 2015 paper.
The key concepts in the Beam programming model are:
PCollection
: represents a collection of data, which could be bounded or unbounded in size.PTransform
: represents a computation that transforms input PCollections into output PCollections.Pipeline
: manages a directed acyclic graph of PTransforms and PCollections that is ready for execution.PipelineRunner
: specifies where and how the pipeline should execute.Beam supports multiple language specific SDKs for writing pipelines against the Beam Model.
Currently, this repository contains SDKs for Java, Python and Go.
Have ideas for new SDKs or DSLs? See the JIRA.
Beam supports executing programs on multiple distributed processing backends through PipelineRunners. Currently, the following PipelineRunners are available:
DirectRunner
runs the pipeline on your local machine.ApexRunner
runs the pipeline on an Apache Hadoop YARN cluster (or in embedded mode).DataflowRunner
submits the pipeline to the Google Cloud Dataflow.FlinkRunner
runs the pipeline on an Apache Flink cluster. The code has been donated from dataArtisans/flink-dataflow and is now part of Beam.SparkRunner
runs the pipeline on an Apache Spark cluster. The code has been donated from cloudera/spark-dataflow and is now part of Beam.Have ideas for new Runners? See the JIRA.
Please refer to the Quickstart[Java, Python, Go] available on our website.
If you'd like to build and install the whole project from the source distribution, you may need some additional tools installed in your system. In a Debian-based distribution:
sudo apt-get install \ openjdk-8-jdk \ python-setuptools \ python-pip \ virtualenv
Then please use the standard ./gradlew build
command.
To get involved in Apache Beam:
We also have a contributor's guide.