Using a central repository
For example, if you are developing using Maven and want to use the SDK for Java with the
DirectRunner, add the following dependencies to your
<dependency> <groupId>org.apache.beam</groupId> <artifactId>beam-sdks-java-core</artifactId> <version>2.25.0</version> </dependency> <dependency> <groupId>org.apache.beam</groupId> <artifactId>beam-runners-direct-java</artifactId> <version>2.25.0</version> <scope>runtime</scope> </dependency>
Similarly in Python, if you are using PyPI and want to use the SDK for Python with
DirectRunner, add the following requirement to your
Additionally, you may want to depend on additional SDK modules, such as IO connectors or other extensions, and additional runners to execute your pipeline at scale.
Downloading source code
You can download the source code package for a release from the links in the Releases section.
You must verify the integrity of downloaded files. We provide OpenPGP signatures for every release file. This signature should be matched against the KEYS file which contains the OpenPGP keys of Apache Beam’s Release Managers. We also provide SHA-512 checksums for every release file (or SHA-1 and MD5 checksums for older releases). After you download the file, you should calculate a checksum for your download, and make sure it is the same as ours.
Apache Beam generally follows the rules of semantic versioning with exceptions. Version numbers use the form
major.minor.incremental and are incremented as follows:
- major version for incompatible API changes
- minor version for new functionality added in a backward-compatible manner, infrequent incompatible API changes
- incremental version for forward-compatible bug fixes
Please note that APIs marked
@Experimental may change at any point and are not guaranteed to remain compatible across versions.
Additionally, any API may change before the first stable release, i.e., between versions denoted