[Announce] Seattle Apache Beam Meetup Group
Hello all, I have just created a meetup group for Apache Beam in the Greater Seattle Area [1]. Please join the group if you would like to be part of a local community group, where we will organize periodic meetups with deep dives, use cases, demos, and all sorts of content about Beam. We are going to host our first Seattle meetup in September; stay tuned for future updates! Thanks, Aizhamal [1] https://www.meetup.com/Seattle-Apache-Beam-Meetup/
Re: [ANNOUNCE] Beam 2.14.0 Released!
Nice work all round! I love the release blog format with the highlights and links to issues. -chad On Thu, Aug 1, 2019 at 4:23 PM Anton Kedin wrote: > The Apache Beam team is pleased to announce the release of version 2.14.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 here: > > https://beam.apache.org/get-started/downloads/ > > This release includes bugfixes, features, and improvements detailed on > the Beam blog: https://beam.apache.org/blog/2019/07/31/beam-2.14.0.html > > Thanks to everyone who contributed to this release, and we hope you enjoy > using Beam 2.14.0. > > -- Anton Kedin, on behalf of The Apache Beam team >
[ANNOUNCE] Beam 2.14.0 Released!
The Apache Beam team is pleased to announce the release of version 2.14.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 here: https://beam.apache.org/get-started/downloads/ This release includes bugfixes, features, and improvements detailed on the Beam blog: https://beam.apache.org/blog/2019/07/31/beam-2.14.0.html Thanks to everyone who contributed to this release, and we hope you enjoy using Beam 2.14.0. -- Anton Kedin, on behalf of The Apache Beam team
Save state on tear down
Hello All, I wondering if there is a way or pattern to save state on tear down ? In case of a failure or a pipeline we cannot update(due to significant changes ) we would like to save the state and re-load it on the next creation of the pipeline. Note: we are currently using Google Dataflow runner Regards, Jose
