[BEAM-10300] Improve JdbcIOTest.testFluentBackOffConfiguration stability (#12517)

* Move commitThread control out of try

* Commit connection on main thread after pipeline has finished.
1 file changed
tree: 472f8c92535191a756b8ef1b1501f8e4aa0bee9b
  1. .asf.yaml
  2. .gitattributes
  3. .github/
  4. .gitignore
  5. .gitmodules
  6. .mailmap
  7. .pre-commit-config.yaml
  8. .test-infra/
  9. .yamllint.yml
  10. CHANGES.md
  11. CI.md
  12. LICENSE
  13. NOTICE
  14. OWNERS
  15. README.md
  16. assembly.xml
  17. build.gradle
  18. buildSrc/
  19. examples/
  20. gradle.properties
  21. gradle/
  22. gradlew
  23. gradlew.bat
  24. learning/
  25. model/
  26. ownership/
  27. release/
  28. runners/
  29. scripts/
  30. sdks/
  31. settings.gradle
  32. vendor/
  33. website/
README.md

Apache Beam

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 Flink, Apache Spark, Google Cloud Dataflow and Hazelcast Jet.

Status

Maven Version PyPI version Build Status Coverage Status Compat Check PyPI Compat Check at master Build python source distribution and wheels

Post-commit tests status (on master branch)

LangSDKDataflowFlinkSamzaSpark
GoBuild Status---Build Status---Build Status
JavaBuild StatusBuild StatusBuild Status
Build Status
Build Status
Build StatusBuild Status
Build Status
PythonBuild Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
---Build Status
XLangBuild Status---Build Status---Build Status

Overview

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.

  1. End Users: Writing pipelines with an existing SDK, running it on an existing runner. These users want to focus on writing their application logic and have everything else just work.
  2. SDK Writers: Developing a Beam SDK targeted at a specific user community (Java, Python, Scala, Go, R, graphical, etc). These users are language geeks, and would prefer to be shielded from all the details of various runners and their implementations.
  3. Runner Writers: Have an execution environment for distributed processing and would like to support programs written against the Beam Model. Would prefer to be shielded from details of multiple SDKs.

The Beam Model

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.

SDKs

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.

Runners

Beam supports executing programs on multiple distributed processing backends through PipelineRunners. Currently, the following PipelineRunners are available:

  • The DirectRunner runs the pipeline on your local machine.
  • The DataflowRunner submits the pipeline to the Google Cloud Dataflow.
  • The FlinkRunner runs the pipeline on an Apache Flink cluster. The code has been donated from dataArtisans/flink-dataflow and is now part of Beam.
  • The SparkRunner runs the pipeline on an Apache Spark cluster. The code has been donated from cloudera/spark-dataflow and is now part of Beam.
  • The JetRunner runs the pipeline on a Hazelcast Jet cluster. The code has been donated from hazelcast/hazelcast-jet and is now part of Beam.
  • The Twister2Runner runs the pipeline on a Twister2 cluster. The code has been donated from DSC-SPIDAL/twister2 and is now part of Beam.

Have ideas for new Runners? See the JIRA.

Getting Started

To learn how to write Beam pipelines, read the Quickstart for [Java, Python, or Go] available on our website.

Contact Us

To get involved in Apache Beam:

Instructions for building and testing Beam itself are in the contribution guide.

More Information