[ANNOUNCE] Apache Beam 2.36.0 Release

The Apache Beam team is pleased to announce the release of version 2.36.0. Apache Beam is an open source unified programming model to define and execute data processing pipelines, including ETL, batch and stream (continuous) processing. See https://beam.apache.org You can download the release

Naming! Dataflow Worker/SDK "Harness" image flag

Hi all, *tl;dr*: keep harness in user-facing container image flag names? I have a few PRs in-progress for "renaming" the workerHarnessContainerImage flag, i.e. adding a new flag and marking the old flag as deprecated. This is being done to better reflect the Portable framework.. I wanted to

Add emilymye to JIRA contributers

Hi dev@ Just realized I didn't request contributor access to JIRA a while back - would someone be able to add me so I can self-assign my issues? Thank you! Emily

Re: [VOTE] Release 2.62.0, release candidate #00

> -1 >> Seems like Dataflow x-lang jobs might be broken for Java 11 users due to >> Java SDK defaulting to Java 11 containers [1] which are not released with >> Beam 2.26.0 [2]. +Emily Ye is looking into this. >> >> Thanks, >> Cham >> >> [1] >> Er

[Announcement] Java container Gradle build task changed to versioned task name

*tl;dr:* sdks:java:container:docker -> sdks:java:container:java8:docker Hi dev@, Starting from https://github.com/apache/beam/pull/13211, we have separated the Java docker build tasks for Java containers by version. Please use the newly versioned Java Docker image build tasks

Re: [ANNOUNCE] Beam Java 8 image rename starting from 2.26.0 (to apache/beam_java8_sdk)

ses so people who are on an older release can migrate now and not have >> to remember to do it with 2.26? >> >> On Tue, Sep 29, 2020 at 5:37 PM Emily Ye wrote: >> >>> Starting with the release of 2.26.0, the Java 8 SDK container image >>> <https

[ANNOUNCE] Beam Java 8 image rename starting from 2.26.0 (to apache/beam_java8_sdk)

Starting with the release of 2.26.0, the Java 8 SDK container image (currently apache/beam_java_sdk ) will be released under a new name, *apache/beam_java8_sdk.* This is in anticipation of

Adding repo to DockerHub for renaming Java8 image

d I thought I'd save next release manager the trouble. Thank you, Emily Ye

Versioning published Java containers

Hi all, I'm getting ramped up on contributing and was looking into adding the Java 11 harness container to releases ( https://issues.apache.org/jira/browse/BEAM-8106) - should I rename the current java container so we have two new images `beam_java8_sdk` and `beam_java11_sdk` or hold off on

[no subject]

Greetings, dev@beam! Just wanted to introduce myself - I'm a SWE at Google who will be contributing to Beam going forward. I'm pretty new to the data processing space but I'm excited to learn, and will probably be asking lots of questions here. Looking forward to getting to know the community!