Re: Hacking a Rust SDK

[Yichi Zhang via dev]

I'm very interested, I admit that I know nothing about Rust but always had
the desire to learn, are there github issues tracking the work?

On Fri, Jan 6, 2023 at 11:09 AM Robert Bradshaw via dev 
wrote:

> Hi all,
>
> Welcome to 2023! As last year, the Google Dataflow team is kicking the
> first week off with a hackathon, and one of the projects proposed this
> year was to throw together a rust SDK. If you're interested, you can
> follow the progress at
> https://github.com/kennknowles/beam/tree/rust/sdks/rust . Even better,
> if you feel so inclined, feel free to chip in! (Though Rust expertise
> would be welcome, don't feel it's necessary--I didn't know it at all
> until this three days ago.) We don't know where it'll go, but it's a
> chance to have some fun and work with new people and maybe learn
> something along the way.
>
> Happy coding!
>
> - Robert
>

Re: [ANNOUNCE] New committer: John Casey

[Yichi Zhang via dev]

Congratulations John!

On Sat, Jul 30, 2022 at 4:23 AM Robert Burke  wrote:

> Woohoo! Congrats John and welcome to committership!
>
> On Fri, Jul 29, 2022, 10:07 PM Kenneth Knowles  wrote:
>
>> Hi all,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new committer:
>> John Casey (johnca...@apache.org)
>>
>> John started contributing to Beam in late 2021. John has quickly become
>> our resident expert on KafkaIO - identifying bugs, making enhancements,
>> helping users - in addition to a variety of other contributions.
>>
>> Considering his contributions to the project over this timeframe, the
>> Beam PMC trusts John with the responsibilities of a Beam committer. [1]
>>
>> Thank you John! And we are looking to see more of your contributions!
>>
>> Kenn, on behalf of the Apache Beam PMC
>>
>> [1]
>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>
>

[ANNOUNCE] Apache Beam 2.39.0 Released

[Yichi Zhang]

The Apache Beam team is pleased to announce the release of version 2.39.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 bug fixes, features, and improvements detailed on the
Beam blog: https://beam.apache.org/blog/beam-2.39.0/

Thanks to everyone who contributed to this release, and we hope you enjoy
using Beam 2.39.0.

-- Yichi Zhang, on behalf of The Apache Beam team

Re: [ANNOUNCE] New committer: Yichi Zhang

[Yichi Zhang]

Thanks everyone! It's my honor and I hope I can make more contributions in
the future!

On Thu, Apr 22, 2021 at 10:11 AM Yichi Zhang  wrote:

> Thanks, Brian!
>
> On Thu, Apr 22, 2021 at 9:11 AM Brian Hulette  wrote:
>
>> Congratulations Yichi!
>>
>> On Thu, Apr 22, 2021 at 8:05 AM Robert Burke  wrote:
>>
>>> Congratulations Yichi!
>>>
>>> On Thu, Apr 22, 2021, 7:17 AM Alexey Romanenko 
>>> wrote:
>>>
>>>> Congratulations, well deserved!
>>>>
>>>> On 22 Apr 2021, at 10:03, Jan Lukavský  wrote:
>>>>
>>>> Congrats Yichi!
>>>> On 4/22/21 4:58 AM, Ahmet Altay wrote:
>>>>
>>>> Congratulations Yichi! 📣📣📣
>>>>
>>>> On Wed, Apr 21, 2021 at 6:48 PM Chamikara Jayalath <
>>>> chamik...@google.com> wrote:
>>>>
>>>>> Congrats Yichi!
>>>>>
>>>>> On Wed, Apr 21, 2021 at 6:14 PM Heejong Lee 
>>>>> wrote:
>>>>>
>>>>>> Congratulations :)
>>>>>>
>>>>>> On Wed, Apr 21, 2021 at 5:20 PM Tomo Suzuki 
>>>>>> wrote:
>>>>>>
>>>>>>> Congratulations!
>>>>>>>
>>>>>>> On Wed, Apr 21, 2021 at 7:48 PM Tyson Hamilton 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Congrats!
>>>>>>>>
>>>>>>>> On Wed, Apr 21, 2021 at 4:37 PM Valentyn Tymofieiev <
>>>>>>>> valen...@google.com> wrote:
>>>>>>>>
>>>>>>>>> Well deserved and congrats, Yichi!
>>>>>>>>>
>>>>>>>>> On Wed, Apr 21, 2021 at 4:23 PM Pablo Estrada 
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Hi all,
>>>>>>>>>>
>>>>>>>>>> Please join me and the rest of the Beam PMC in welcoming a new
>>>>>>>>>> committer: Yichi Zhang
>>>>>>>>>>
>>>>>>>>>> Yichi has been working in Beam for a while. He has contributed to
>>>>>>>>>> various areas, including Nexmark tests, test health, Python's 
>>>>>>>>>> streaming
>>>>>>>>>> capabilities, he has answered questions on StackOverflow, and helped 
>>>>>>>>>> with
>>>>>>>>>> release validations, among many other things that Yichi has 
>>>>>>>>>> contributed to
>>>>>>>>>> the Beam community.
>>>>>>>>>>
>>>>>>>>>> Considering these contributions, the Beam PMC trusts Yichi with
>>>>>>>>>> the responsibilities of a Beam committer.[1]
>>>>>>>>>>
>>>>>>>>>> Thanks Yichi!
>>>>>>>>>> -P.
>>>>>>>>>>
>>>>>>>>>> [1]
>>>>>>>>>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Regards,
>>>>>>> Tomo
>>>>>>>
>>>>>>
>>>>

Re: [ANNOUNCE] New committer: Tomo Suzuki

[Yichi Zhang]

Congratulations!

On Fri, Apr 2, 2021 at 9:42 AM Ahmet Altay  wrote:

> Congratulations! 🎉🎉🎉
>
> On Fri, Apr 2, 2021 at 9:38 AM Kenneth Knowles  wrote:
>
>> Hi all,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new committer:
>> Tomo Suzuki
>>
>> Since joining the Beam community in 2019, Tomo has done lots of critical
>> work on Beam's dependencies: maintaining the dependency checker that files
>> Jiras and sends emails, upgrading dependencies, fixing dependency
>> configuration errors, maintaining our linkage checker. Most recently, an
>> epic upgrade of gRPC.
>>
>> Considering these highlighted contributions and the rest, the Beam PMC
>> trusts Tomo with the responsibilities of a Beam committer [1].
>>
>> Thank you, Tomo, for your contributions.
>>
>> Kenn
>>
>> [1] https://beam.apache.org/contribute/become-a-committer
>> /#an-apache-beam-committer
>>
>

Re: [ANNOUNCE] New committer: Ning Kang

[Yichi Zhang]

Congratulations Ning!

On Tue, Mar 23, 2021 at 1:00 PM Robin Qiu  wrote:

> Congratulations Ning!
>
> On Tue, Mar 23, 2021 at 12:56 PM Ahmet Altay  wrote:
>
>> Congratulations Ning!
>>
>> On Tue, Mar 23, 2021 at 12:38 PM Alexey Romanenko <
>> aromanenko@gmail.com> wrote:
>>
>>> Congrats, Ning Kang! Well deserved!
>>> Thank you for your contributions and users support!
>>>
>>> Alexey
>>>
>>> On 23 Mar 2021, at 20:35, Pablo Estrada  wrote:
>>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new
>>> committer: Ning Kang.
>>>
>>> Ning has been working in Beam for a while. He has contributed to the
>>> interactive experience of the Pyhton SDK, and developed a sidebar
>>> component, along with a release process for it. Ning has also helped users
>>> on StackOverflow and user@, especially when it comes to Interactive
>>> Beam.
>>>
>>> Considering these contributions, the Beam PMC trusts Ning with the
>>> responsibilities of a Beam committer.[1]
>>>
>>> Thanks Ning!
>>> -P.
>>>
>>> [1] https://beam.apache.org/contribute/become-a-committer
>>> /#an-apache-beam-committer
>>>
>>>
>>>

Re: [VOTE] Release 2.28.0, release candidate #1

[Yichi Zhang]

nvm, it is broken on master but not broken for the release.

+1

On Fri, Feb 19, 2021 at 4:48 PM Yichi Zhang  wrote:

> -1
> I ran the python sdk prebuilding workflow and it seems to be broken with
> dataflow_python_sdk.tar not found will investigate into it.
>
> On Fri, Feb 19, 2021 at 2:03 PM Robert Bradshaw 
> wrote:
>
>> +1 (binding)
>>
>> I validated the signatures and package contents, as well as running a
>> small Python pipeline in a fresh virtual environment.
>>
>> On Fri, Feb 19, 2021 at 1:36 PM Chamikara Jayalath 
>> wrote:
>>
>>> +1
>>>
>>> I ran the release candidate verification script and updated the
>>> spreadsheet [1]
>>> Also, verified signature and checksums of some of the artifacts.
>>>
>>> Thanks,
>>> Cham
>>>
>>> [1]
>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=283321283
>>>
>>>
>>> On Thu, Feb 18, 2021 at 2:19 PM Brian Hulette 
>>> wrote:
>>>
>>>> +1 (non-binding)
>>>>
>>>> Built and ran a streaming SQL in Python pipeline and a DataFrame API
>>>> pipeline on Dataflow
>>>>
>>>> On Thu, Feb 18, 2021 at 1:00 PM Pablo Estrada 
>>>> wrote:
>>>>
>>>>> +1 (binding)
>>>>>
>>>>> Built and ran basic tests for existing Dataflow templates
>>>>>
>>>>> On Wed, Feb 17, 2021 at 8:06 PM Chamikara Jayalath <
>>>>> chamik...@google.com> wrote:
>>>>>
>>>>>> Repositories were merged into [1]. So this RC validation thread can
>>>>>> continue.
>>>>>>
>>>>>> Thanks,
>>>>>> Cham
>>>>>>
>>>>>> [1]
>>>>>> https://repository.apache.org/content/repositories/orgapachebeam-1161/
>>>>>>
>>>>>> On Wed, Feb 17, 2021 at 10:41 AM Chamikara Jayalath <
>>>>>> chamik...@google.com> wrote:
>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> FYI: I noticed that one of the Java artifacts was pushed into a
>>>>>>> separate Nexus repository for some reason.
>>>>>>> https://issues.apache.org/jira/browse/BEAM-11813 is tracking this
>>>>>>> and we are trying to get the two repos merged but this should not block
>>>>>>> release candidate validation.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Cham
>>>>>>>
>>>>>>> On Wed, Feb 17, 2021 at 10:32 AM Valentyn Tymofieiev <
>>>>>>> valen...@google.com> wrote:
>>>>>>>
>>>>>>>> +1.
>>>>>>>> I ran several Python pipelines on Direct and Dataflow runner
>>>>>>>> and inspected Dataflow container images.
>>>>>>>>
>>>>>>>> CHANGES.md[1]  has a nice long list of new features. I encourage
>>>>>>>> authors of the features to verify them on the RC and vote here.
>>>>>>>> [1] https://github.com/chamikaramj/beam/blob/blog_2_28_0/CHANGES.md
>>>>>>>>
>>>>>>>> On Mon, Feb 15, 2021 at 12:02 PM Chamikara Jayalath <
>>>>>>>> chamik...@google.com> wrote:
>>>>>>>>
>>>>>>>>> Hi everyone,
>>>>>>>>>
>>>>>>>>> Please review and vote on the release candidate #1 for the version
>>>>>>>>> 2.28.0, as follows:
>>>>>>>>> [ ] +1, Approve the release
>>>>>>>>> [ ] -1, Do not approve the release (please provide specific
>>>>>>>>> comments)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Reviewers are encouraged to test their own use cases with the
>>>>>>>>> release candidate, and vote +1 if no issues are found.
>>>>>>>>>
>>>>>>>>> The complete staging area is available for your review, which
>>>>>>>>> includes:
>>>>>>>>> * JIRA release notes [1],
>>>>>>>>> * the official Apache source release to be deployed to
>>>>>>>>> dist.apache.org [2], which is signed with the key with
>>>>>>>>> fingerprint 0CCD5EB2A718A56E [3],
>>>>>>>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>>>>>>>> * source code tag "v2.28.0-RC1" [5],
>>>>>>>>> * website pull request listing the release [6], publishing the API
>>>>>>>>> reference manual [7], and the blog post [8].
>>>>>>>>> * Java artifacts were built with Maven 3.3.9 and OpenJDK/Oracle
>>>>>>>>> JDK 1.8.0_181.
>>>>>>>>> * Python artifacts are deployed along with the source release to
>>>>>>>>> the dist.apache.org [2].
>>>>>>>>> * Validation sheet with a tab for 2.28.0 release to help with
>>>>>>>>> validation [9].
>>>>>>>>> * Docker images published to Docker Hub [10].
>>>>>>>>>
>>>>>>>>> The vote will be open for at least 72 hours. It is adopted by
>>>>>>>>> majority approval, with at least 3 PMC affirmative votes.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Cham
>>>>>>>>>
>>>>>>>>> [1]
>>>>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12349499
>>>>>>>>> [2] https://dist.apache.org/repos/dist/dev/beam/2.28.0/
>>>>>>>>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>>>>>>>> [4]
>>>>>>>>> https://repository.apache.org/content/repositories/orgapachebeam-1161/
>>>>>>>>> [5] https://github.com/apache/beam/tree/v2.28.0-RC1
>>>>>>>>> [6] https://github.com/apache/beam/pull/13991
>>>>>>>>> [7] https://github.com/apache/beam-site/pull/611
>>>>>>>>> [8] https://github.com/apache/beam/pull/13992
>>>>>>>>> [9]
>>>>>>>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=283321283
>>>>>>>>> [10] https://hub.docker.com/search?q=apache%2Fbeam&type=image
>>>>>>>>>
>>>>>>>>

Re: [VOTE] Release 2.28.0, release candidate #1

[Yichi Zhang]

-1
I ran the python sdk prebuilding workflow and it seems to be broken with
dataflow_python_sdk.tar not found will investigate into it.

On Fri, Feb 19, 2021 at 2:03 PM Robert Bradshaw  wrote:

> +1 (binding)
>
> I validated the signatures and package contents, as well as running a
> small Python pipeline in a fresh virtual environment.
>
> On Fri, Feb 19, 2021 at 1:36 PM Chamikara Jayalath 
> wrote:
>
>> +1
>>
>> I ran the release candidate verification script and updated the
>> spreadsheet [1]
>> Also, verified signature and checksums of some of the artifacts.
>>
>> Thanks,
>> Cham
>>
>> [1]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=283321283
>>
>>
>> On Thu, Feb 18, 2021 at 2:19 PM Brian Hulette 
>> wrote:
>>
>>> +1 (non-binding)
>>>
>>> Built and ran a streaming SQL in Python pipeline and a DataFrame API
>>> pipeline on Dataflow
>>>
>>> On Thu, Feb 18, 2021 at 1:00 PM Pablo Estrada 
>>> wrote:
>>>
 +1 (binding)

 Built and ran basic tests for existing Dataflow templates

 On Wed, Feb 17, 2021 at 8:06 PM Chamikara Jayalath <
 chamik...@google.com> wrote:

> Repositories were merged into [1]. So this RC validation thread can
> continue.
>
> Thanks,
> Cham
>
> [1]
> https://repository.apache.org/content/repositories/orgapachebeam-1161/
>
> On Wed, Feb 17, 2021 at 10:41 AM Chamikara Jayalath <
> chamik...@google.com> wrote:
>
>> Thanks.
>>
>> FYI: I noticed that one of the Java artifacts was pushed into a
>> separate Nexus repository for some reason.
>> https://issues.apache.org/jira/browse/BEAM-11813 is tracking this
>> and we are trying to get the two repos merged but this should not block
>> release candidate validation.
>>
>> Thanks,
>> Cham
>>
>> On Wed, Feb 17, 2021 at 10:32 AM Valentyn Tymofieiev <
>> valen...@google.com> wrote:
>>
>>> +1.
>>> I ran several Python pipelines on Direct and Dataflow runner
>>> and inspected Dataflow container images.
>>>
>>> CHANGES.md[1]  has a nice long list of new features. I encourage
>>> authors of the features to verify them on the RC and vote here.
>>> [1] https://github.com/chamikaramj/beam/blob/blog_2_28_0/CHANGES.md
>>>
>>> On Mon, Feb 15, 2021 at 12:02 PM Chamikara Jayalath <
>>> chamik...@google.com> wrote:
>>>
 Hi everyone,

 Please review and vote on the release candidate #1 for the version
 2.28.0, as follows:
 [ ] +1, Approve the release
 [ ] -1, Do not approve the release (please provide specific
 comments)


 Reviewers are encouraged to test their own use cases with the
 release candidate, and vote +1 if no issues are found.

 The complete staging area is available for your review, which
 includes:
 * JIRA release notes [1],
 * the official Apache source release to be deployed to
 dist.apache.org [2], which is signed with the key with fingerprint
 0CCD5EB2A718A56E [3],
 * all artifacts to be deployed to the Maven Central Repository [4],
 * source code tag "v2.28.0-RC1" [5],
 * website pull request listing the release [6], publishing the API
 reference manual [7], and the blog post [8].
 * Java artifacts were built with Maven 3.3.9 and OpenJDK/Oracle JDK
 1.8.0_181.
 * Python artifacts are deployed along with the source release to
 the dist.apache.org [2].
 * Validation sheet with a tab for 2.28.0 release to help with
 validation [9].
 * Docker images published to Docker Hub [10].

 The vote will be open for at least 72 hours. It is adopted by
 majority approval, with at least 3 PMC affirmative votes.

 Thanks,
 Cham

 [1]
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12349499
 [2] https://dist.apache.org/repos/dist/dev/beam/2.28.0/
 [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 [4]
 https://repository.apache.org/content/repositories/orgapachebeam-1161/
 [5] https://github.com/apache/beam/tree/v2.28.0-RC1
 [6] https://github.com/apache/beam/pull/13991
 [7] https://github.com/apache/beam-site/pull/611
 [8] https://github.com/apache/beam/pull/13992
 [9]
 https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=283321283
 [10] https://hub.docker.com/search?q=apache%2Fbeam&type=image

>>>

Re: [ANNOUNCE] New committer: Piotr Szuberski

[Yichi Zhang]

Congrats Piotrek!

On Fri, Jan 22, 2021 at 10:02 AM Robert Burke  wrote:

> Congrats Piotr!
>
> On Fri, Jan 22, 2021, 10:00 AM Tobiasz Kędzierski <
> tobiasz.kedzier...@polidea.com> wrote:
>
>> Congrats Piotrek!
>>
>> On Fri, Jan 22, 2021 at 6:54 PM Brian Hulette 
>> wrote:
>>
>>> Congratulations Piotr, and thank you for all your contributions!
>>>
>>> On Fri, Jan 22, 2021 at 9:45 AM Robert Bradshaw 
>>> wrote:
>>>
 Thanks, Piotr. Well deserved.

 On Fri, Jan 22, 2021 at 9:22 AM Tyson Hamilton 
 wrote:

> Congrats Piotr! Well deserved.
>
> On Fri, Jan 22, 2021 at 9:18 AM Ismaël Mejía 
> wrote:
>
>> Congratulations Piotr ! Thanks for all your work !
>>
>> On Fri, Jan 22, 2021 at 5:33 PM Alexey Romanenko
>>  wrote:
>> >
>> > Hi everyone,
>> >
>> > Please join me and the rest of the Beam PMC in welcoming a new
>> committer: Piotr Szuberski .
>> >
>> > Piotr started to contribute to Beam about one year ago and he did
>> it very actively since then. He contributed to the different areas, like
>> adding a cross-language functionality to existing IOs, improving ITs and
>> performance tests environment/runtime, he actively worked on dependency
>> updates [1].
>> >
>> > In consideration of his contributions, the Beam PMC trusts him with
>> the responsibilities of a Beam committer [2].
>> >
>> > Thank you for your contributions, Piotr!
>> >
>> > -Alexey, on behalf of the Apache Beam PMC
>> >
>> > [1]
>> https://github.com/apache/beam/pulls?q=is%3Apr+author%3Apiotr-szuberski
>> > [2]
>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>> >
>> >
>>
>

Re: [ANNOUNCE] New PMC Member: Chamikara Jayalath

[Yichi Zhang]

Congrats Cham!

On Fri, Jan 22, 2021 at 8:34 AM Alexey Romanenko 
wrote:

> Congrats, Cham! Thank you for your work!
>
> On 22 Jan 2021, at 09:53, Gleb Kanterov  wrote:
>
> Congratulations!
>
> On Fri, Jan 22, 2021 at 9:29 AM Ismaël Mejía  wrote:
>
>> Congrats Cham, well deserved!
>>
>>
>> On Fri, Jan 22, 2021 at 9:02 AM Michał Walenia <
>> michal.wale...@polidea.com> wrote:
>>
>>> Congratulations, Cham! Thanks for your work!
>>>
>>>
>>> On Fri, Jan 22, 2021 at 3:13 AM Charles Chen  wrote:
>>>
 Congrats Cham!

 On Thu, Jan 21, 2021, 5:39 PM Chamikara Jayalath 
 wrote:

> Thanks everybody :)
>
> - Cham
>
> On Thu, Jan 21, 2021 at 5:22 PM Pablo Estrada 
> wrote:
>
>> Yoohoo Cham : )
>>
>> On Thu, Jan 21, 2021 at 5:20 PM Udi Meiri  wrote:
>>
>>> Congrats Cham!
>>>
>>> On Thu, Jan 21, 2021 at 4:25 PM Griselda Cuevas 
>>> wrote:
>>>
 Congratulations Cham!!! Well deserved :)

 On Thu, 21 Jan 2021 at 15:23, Connell O'Callaghan <
 conne...@google.com> wrote:

> Well done Cham!!! Thank you for all your contributions to date!!!
>
>
> On Thu, Jan 21, 2021 at 3:18 PM Rui Wang 
> wrote:
>
>> Congratulations, Cham!
>>
>> -Rui
>>
>> On Thu, Jan 21, 2021 at 3:15 PM Robert Bradshaw <
>> rober...@google.com> wrote:
>>
>>> Congratulations, Cham!
>>>
>>> On Thu, Jan 21, 2021 at 3:13 PM Brian Hulette <
>>> bhule...@google.com> wrote:
>>>
 Great news, congratulations Cham!

 On Thu, Jan 21, 2021 at 3:08 PM Robin Qiu 
 wrote:

> Congratulations, Cham!
>
> On Thu, Jan 21, 2021 at 3:05 PM Tyson Hamilton <
> tyso...@google.com> wrote:
>
>> Woo! Congrats Cham!
>>
>> On Thu, Jan 21, 2021 at 3:02 PM Robert Burke <
>> rob...@frantil.com> wrote:
>>
>>> Congratulations! That's fantastic news.
>>>
>>> On Thu, Jan 21, 2021, 2:59 PM Reza Rokni 
>>> wrote:
>>>
 Congratulations!

 On Fri, Jan 22, 2021 at 6:58 AM Ankur Goenka <
 goe...@google.com> wrote:

> Congrats Cham!
>
> On Thu, Jan 21, 2021 at 2:57 PM Ahmet Altay <
> al...@google.com> wrote:
>
>> Hi all,
>>
>> Please join me and the rest of Beam PMC in welcoming
>> Chamikara Jayalath as our
>> newest PMC member.
>>
>> Cham has been part of the Beam community from its early
>> days and contributed to the project in significant ways, 
>> including
>> contributing new features and improvements especially 
>> related Beam IOs,
>> advocating for users, and mentoring new community members.
>>
>> Congratulations Cham! And thanks for being a part of Beam!
>>
>> Ahmet
>>
>
>>>
>>> --
>>> Michał Walenia
>>> Polidea  | Software Engineer
>>> M: +48 791 432 002 <+48791432002>
>>> E: michal.wale...@polidea.com
>>> Unique Tech
>>> Check out our projects! 
>>>
>>
>

Re: [PROPOSAL] Preparing for Beam 2.28.0 release

[Yichi Zhang]

Thank you, Cham!

On Wed, Jan 13, 2021 at 12:58 PM Ahmet Altay  wrote:

> Thank you Cham!
>
> On Wed, Jan 13, 2021 at 12:44 PM Rui Wang  wrote:
>
>> Thanks Cham for working on this!
>>
>>
>> -Rui
>>
>> On Wed, Jan 13, 2021 at 11:32 AM Kyle Weaver  wrote:
>>
>>> Thanks for stepping up Cham!
>>>
>>> Remember to mark critical JIRA issues as release blockers everybody!
>>>
>>> On Wed, Jan 13, 2021 at 11:25 AM Chamikara Jayalath <
>>> chamik...@google.com> wrote:
>>>
 Hi All,

 Beam 2.28.0 release is scheduled to be cut on January 27th according to
 the release calendar [1]

 I'd like to volunteer myself to be the release manager for this
 release. I plan on cutting the release branch on the scheduled date.

 Any comments or objections ?

 Thanks,
 Cham

 [1]
 https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com&ctz=America/Los_Angeles

>>>

Re: [VOTE] Release 2.27.0, release candidate #4

[Yichi Zhang]

+1, I verified the python mobile game walkthrough on core runners.

On Thu, Jan 7, 2021 at 8:29 AM Valentyn Tymofieiev 
wrote:

> On Thu, Jan 7, 2021 at 8:06 AM Ismaël Mejía  wrote:
>
>> > Also I wonder if we now need to clarify both Java 8 and Java 11
>> versions separately?
>>
>> You mean for the docker images? Otherwise we should not be using Java
>> 11 at all to produce the artifacts.
>>
>
> Thanks for clarification, yes, looks like Docker images are the only
> artifacts where this concern applies.  The Docker images include several
> jars[1], that I believe are currently built locally (by a release manager
> at container image build time). Are the jars included in Java 11 images
> built with Java 11? If so, is it worth calling out the compiler?  Also,
> perhaps we should look into building release artifacts using Jenkins or
> Github Actions, with a preconfigured version of compilers, instead of
> whatever version is installed on the release manager's machine.
>
> [1]
> https://github.com/apache/beam/blob/master/sdks/java/container/Dockerfile#L24-L33
>
>
>>
>> On Thu, Jan 7, 2021 at 4:51 PM Valentyn Tymofieiev 
>> wrote:
>> >
>> > Noting that announcement does not include the version of the Java
>> compilers used - looks like the release guide still requires it:
>> >
>> > * Java artifacts were built with Maven MAVEN_VERSION and OpenJDK/Oracle
>> JDK JDK_VERSION.
>> >
>> >
>> > Could you please add this info to this thread for posterity?
>> >
>> > Also I wonder if we now need to clarify both Java 8 and Java 11
>> versions separately?
>> >
>> > Other than that, +1 from me. Ran several mobile gaming pipelines on
>> Direct and Dataflow runners with Python 3.8.
>> >
>> > On Thu, Jan 7, 2021 at 12:49 AM Jan Lukavský  wrote:
>> >>
>> >> +1 (non-binding).
>> >>
>> >> I've validated the RC against my dependent projects (mainly Java SDK,
>> Flink and DirectRunner).
>> >>
>> >> Thanks,
>> >>
>> >>  Jan
>> >>
>> >> On 1/7/21 2:15 AM, Ahmet Altay wrote:
>> >>
>> >> +1 (binding) - validated python quickstarts.
>> >>
>> >> Thank you Pablo.
>> >>
>> >> On Wed, Jan 6, 2021 at 1:57 PM Pablo Estrada 
>> wrote:
>> >>>
>> >>> +1 (binding)
>> >>> I've built and unit tested existing Dataflow Templates with the new
>> version.
>> >>> Best
>> >>> -P.
>> >>>
>> >>> On Tue, Jan 5, 2021 at 11:17 PM Pablo Estrada 
>> wrote:
>> 
>>  Hi everyone,
>>  Please review and vote on the release candidate #4 for the version
>> 2.27.0, as follows:
>>  [ ] +1, Approve the release
>>  [ ] -1, Do not approve the release (please provide specific comments)
>> 
>>  NOTE. What happened to RC #2? I started building RC2 before
>> completing all the cherry-picks, so the tag for RC2 was created on an
>> incorrect commit.
>> 
>>  NOTE. What happened to RC #3? I started building RC3, but a new bug
>> was discovered (BEAM-11569) that required amending the branch. Thus this is
>> now RC4.
>> 
>>  Reviewers are encouraged to test their own use cases with the
>> release candidate, and vote +1
>>   if no issues are found.
>> 
>>  The complete staging area is available for your review, which
>> includes:
>>  * JIRA release notes [1],
>>  * the official Apache source release to be deployed to
>> dist.apache.org [2], which is signed with the key with fingerprint
>> C79DDD47DAF3808F0B9DDFAC02B2D9F742008494 [3],
>>  * all artifacts to be deployed to the Maven Central Repository [4],
>>  * source code tag "v2.27.0-RC4" [5],
>>  * website pull request listing the release [6], publishing the API
>> reference manual [7], and the blog post [8].
>>  * Python artifacts are deployed along with the source release to the
>> dist.apache.org [2].
>>  * Validation sheet with a tab for 2.27.0 release to help with
>> validation [9].
>>  * Docker images published to Docker Hub [10].
>> 
>>  The vote will be open for at least 72 hours, but given the holidays,
>> we will likely extend for a few more days. The release will be adopted by
>> majority approval, with at least 3 PMC affirmative votes.
>> 
>>  Thanks,
>>  -P.
>> 
>>  [1]
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12349380
>>  [2] https://dist.apache.org/repos/dist/dev/beam/2.27.0/
>>  [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>  [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1149/
>>  [5] https://github.com/apache/beam/tree/v2.27.0-RC4
>>  [6] https://github.com/apache/beam/pull/13602
>>  [7] https://github.com/apache/beam-site/pull/610
>>  [8] https://github.com/apache/beam/pull/13603
>>  [9]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=194829106
>>  [10] https://hub.docker.com/search?q=apache%2Fbeam&type=image
>>
>

Re: Standarizing the "Runner" concept across website content

[Yichi Zhang]

I agree with what kenn said, in most cases I would refer to the term runner
as the adapter for translating user's pipeline code into a job
representation and submitting it to the execution engine. Though in some
cases they may still be used interchangeably such as direct runner?

On Wed, Jan 6, 2021 at 11:02 AM Kenneth Knowles  wrote:

> I personally try to always distinguish two concepts: the thing doing the
> computing (like Spark or Flink), and the adapter for running a Beam
> pipeline (like SparkRunner or FlinkRunner). I use the term "runner" to mean
> the adapter, and have been trying to use the term "engine" to refer to the
> thing doing the computing. Do you think that users will use these two
> interchangeably? Do you have recommendations about if these terms makes
> sense to users?
>
> Kenn
>
> On Wed, Jan 6, 2021 at 10:23 AM Griselda Cuevas  wrote:
>
>> Hi dev@ community, Happy New Year!
>>
>> I'm working on updating the copy of a few website pages, and something
>> that I want to solve is standardize how we refer to runners across the
>> site. So far I've identified these definitions:
>>
>>- Back-end
>>- Backend systems
>>- Execution environments
>>- Runtime
>>- Runtime system
>>- Runner
>>
>> Even when the majority of users will understand these concepts
>> interchangeably, it's a good idea to be consistent so new users get
>> familiar with how Beam works and its components.
>>
>> I'm going to start using the word "Runner" as I update the copy and will
>> ask the team working in te UI revamp to do the same. Let me know if you
>> have any questions/concerns.
>>
>

Re: Dynamic timers in python sdk.

[Yichi Zhang]

Fair enough, I think we can also just extend existing timer API to allow
setting a dynamic timer tag field:

timer.set(timestamp) -> timer.set(timestamp, dynamic_timer_tag=a_tag)
timer.clear() -> timer.clear(dynamic_timer_tag=a_tag)

and have the default value of dynamic_timer_tag to be empty (the special
case)

On Wed, Dec 9, 2020 at 5:12 PM Robert Bradshaw  wrote:

> On Wed, Dec 9, 2020 at 3:48 PM Kyle Weaver  wrote:
>
>> Possibly a dumb question, but: if "the static timer is just a special
>> case of the dynamic timer," why do we need to use different classes at all?
>>
>
> I agree, I would argue that there is little if any value to the user
> to distinguish between these two "types" of timers at all.
>
>
>> On Wed, Dec 9, 2020 at 2:30 PM Yichi Zhang  wrote:
>>
>>> Hi, Beam community,
>>>
>>> I'm trying to add the dynamic timer
>>> <https://issues.apache.org/jira/browse/BEAM-6857> support to the python
>>> sdk. In java sdk, a dynamic timer is specified through declaring a
>>> TimerSpec of timerMap type and annotating it with @TimerFamily in
>>> process method parameter:
>>>
>>>   @TimerFamily("timers") private final TimerSpec timer =
>>> TimerSpecs.timerMap(TimeDomain.EVENT_TIME);
>>>
>>>   @ProcessElement public void process(
>>>   @Element KV element,
>>>   @Timestamp Instant elementTs,
>>>   @TimerFamily("timers") TimerMap timers) {
>>>  timers.set(element.getValue().getActionType(), elementTs);
>>>   }
>>>
>>>
>>> In python, I'm trying to figure out how we should differentiate a
>>> dynamic timer to the conventional static timer, at the timer spec
>>> declaration or process parameters annotation, or both:
>>>
>>> Approach 1: if we differentiate them only at timer spec declaration it
>>> looks like:
>>>
>>> class TimerDoFn(beam.DoFn):
>>>   timer_spec = userstate.TimerSpec('static_timer', 
>>> userstate.TimeDomain.WATERMARK)
>>>   timer_family_spec = userstate.TimerFamilySpec('dynamic_timer', 
>>> userstate.TimeDomain.WATERMARK)
>>>   def process(self,
>>>   element,
>>>   timer=beam.DoFn.TimerParam(timer_spec),
>>>   timer_map=beam.DoFn.TimerParam(timer_family_spec)):
>>>
>>>   @userstate.on_timer(timer_spec)
>>>   def process_timer(
>>>   self,
>>>   ts=beam.DoFn.TimestampParam,
>>>   timer=beam.DoFn.TimerParam(timer_spec)):
>>>
>>>   @userstate.on_timer(timer_family_spec)
>>>   def process_timer_map(
>>>   self,
>>>   ts=beam.DoFn.TimestampParam,
>>>   dynamic_tag=DoFn.DynamicTagParam,
>>>   timer_map=beam.DoFn.TimerParam(timer_family_spec))
>>>
>>> Approach 2: if only at parameter annotation:
>>>
>>> class TimerDoFn(beam.DoFn):
>>>   timer_spec = userstate.TimerSpec('static_timer', 
>>> userstate.TimeDomain.WATERMARK)
>>>   timer_family_spec = userstate.TimerSpec('dynamic_timer', 
>>> userstate.TimeDomain.WATERMARK)
>>>   def process(self,
>>>   element,
>>>   timer=beam.DoFn.TimerParam(timer_spec),
>>>   timer_map=beam.DoFn.TimerFamilyParam(timer_family_spec)):
>>>
>>>   @userstate.on_timer(timer_spec)
>>>   def process_timer(
>>>   self,
>>>   ts=beam.DoFn.TimestampParam,
>>>   timer=beam.DoFn.TimerParam(timer_spec)):
>>>
>>>   @userstate.on_timer(timer_family_spec)
>>>   def process_timer(
>>>   self,
>>>   ts=beam.DoFn.TimestampParam,
>>>   timer=beam.DoFn.TimerFamilyParam(timer_family_spec)):
>>>
>>>
>>> Approach 3: we can differentiate them at both places, but since the
>>> static timer is just a special case of the dynamic timer, it will introduce
>>> a certain amount of code duplication.
>>>
>>> I'm trying to decide which one offers the best API readability and
>>> usability.
>>>
>>> Anyone have any opinions?
>>>
>>> Thanks,
>>> Yichi
>>>
>>

Dynamic timers in python sdk.

[Yichi Zhang]

Hi, Beam community,

I'm trying to add the dynamic timer
 support to the python
sdk. In java sdk, a dynamic timer is specified through declaring a
TimerSpec of timerMap type and annotating it with @TimerFamily in
process method parameter:

  @TimerFamily("timers") private final TimerSpec timer =
TimerSpecs.timerMap(TimeDomain.EVENT_TIME);

  @ProcessElement public void process(
  @Element KV element,
  @Timestamp Instant elementTs,
  @TimerFamily("timers") TimerMap timers) {
 timers.set(element.getValue().getActionType(), elementTs);
  }


In python, I'm trying to figure out how we should differentiate a dynamic
timer to the conventional static timer, at the timer spec declaration or
process parameters annotation, or both:

Approach 1: if we differentiate them only at timer spec declaration it
looks like:

class TimerDoFn(beam.DoFn):
  timer_spec = userstate.TimerSpec('static_timer',
userstate.TimeDomain.WATERMARK)
  timer_family_spec = userstate.TimerFamilySpec('dynamic_timer',
userstate.TimeDomain.WATERMARK)
  def process(self,
  element,
  timer=beam.DoFn.TimerParam(timer_spec),
  timer_map=beam.DoFn.TimerParam(timer_family_spec)):

  @userstate.on_timer(timer_spec)
  def process_timer(
  self,
  ts=beam.DoFn.TimestampParam,
  timer=beam.DoFn.TimerParam(timer_spec)):

  @userstate.on_timer(timer_family_spec)
  def process_timer_map(
  self,
  ts=beam.DoFn.TimestampParam,
  dynamic_tag=DoFn.DynamicTagParam,
  timer_map=beam.DoFn.TimerParam(timer_family_spec))

Approach 2: if only at parameter annotation:

class TimerDoFn(beam.DoFn):
  timer_spec = userstate.TimerSpec('static_timer',
userstate.TimeDomain.WATERMARK)
  timer_family_spec = userstate.TimerSpec('dynamic_timer',
userstate.TimeDomain.WATERMARK)
  def process(self,
  element,
  timer=beam.DoFn.TimerParam(timer_spec),
  timer_map=beam.DoFn.TimerFamilyParam(timer_family_spec)):

  @userstate.on_timer(timer_spec)
  def process_timer(
  self,
  ts=beam.DoFn.TimestampParam,
  timer=beam.DoFn.TimerParam(timer_spec)):

  @userstate.on_timer(timer_family_spec)
  def process_timer(
  self,
  ts=beam.DoFn.TimestampParam,
  timer=beam.DoFn.TimerFamilyParam(timer_family_spec)):


Approach 3: we can differentiate them at both places, but since the static
timer is just a special case of the dynamic timer, it will introduce a
certain amount of code duplication.

I'm trying to decide which one offers the best API readability and
usability.

Anyone have any opinions?

Thanks,
Yichi

Re: [ANNOUNCE] New committer: Heejong Lee

[Yichi Zhang]

Congratulations Heejong!

On Tue, Sep 8, 2020 at 1:42 PM Ankur Goenka  wrote:

> Congratulations Heejong!
>
> On Tue, Sep 8, 2020 at 1:40 PM Udi Meiri  wrote:
>
>> Congrats Heejong!
>>
>> On Tue, Sep 8, 2020 at 12:33 PM Tyson Hamilton 
>> wrote:
>>
>>> Congratulations!
>>>
>>> On Tue, Sep 8, 2020, 12:10 PM Robert Bradshaw 
>>> wrote:
>>>
 Congratulations, Heejong!

 On Tue, Sep 8, 2020 at 11:41 AM Rui Wang  wrote:

> Congrats, Heejong!
>
>
> -Rui
>
> On Tue, Sep 8, 2020 at 11:26 AM Robin Qiu  wrote:
>
>> Congrats, Heejong!
>>
>> On Tue, Sep 8, 2020 at 11:23 AM Valentyn Tymofieiev <
>> valen...@google.com> wrote:
>>
>>> Congratulations, Heejong!
>>>
>>> On Tue, Sep 8, 2020 at 11:14 AM Ahmet Altay 
>>> wrote:
>>>
 Hi everyone,

 Please join me and the rest of the Beam PMC in welcoming
 a new committer: Heejong Lee .

 Heejong has been active in the community for more than 2 years,
 worked on various IOs (parquet, kafka, file, pubsub) and most recently
 worked on adding cross language transforms feature to Beam [1].

 In consideration of his contributions, the Beam PMC trusts him with
 the responsibilities of a Beam committer [2].

 Thank you for your contributions Heejong!

 -Ahmet, on behalf of the Apache Beam PMC

 [1]
 https://issues.apache.org/jira/browse/BEAM-10634?jql=project%20%3D%20BEAM%20AND%20assignee%20in%20(heejong)%20ORDER%20BY%20resolved%20DESC%2C%20affectedVersion%20ASC%2C%20priority%20DESC%2C%20updated%20DESC
 [2]
 https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer

>>>

Re: Output timestamp for Python event timers

[Yichi Zhang]

+1 to expose set_output_timestamp and enrich python set timer api.

On Tue, Aug 11, 2020 at 12:01 PM Boyuan Zhang  wrote:

> Hi Maximilian,
>
> It makes sense to set  hold_timestamp as fire_timestamp when the
> fire_timestamp is in the event time domain. Otherwise, the system may
> advance the watermark incorrectly.
> I think we can do something similar to Java FnApiRunner[1]:
>
>- Expose set_output_timestamp API to python timer as well
>- If set_output_timestamp is not specified and timer is in event
>domain, we can use fire_timestamp as hold_timestamp
>- Otherwise, use input_timestamp as hold_timestamp.
>
> What do you think?
>
> [1]
> https://github.com/apache/beam/blob/edb42952f6b0aa99477f5c7baca6d6a0d93deb4f/sdks/java/harness/src/main/java/org/apache/beam/fn/harness/FnApiDoFnRunner.java#L1433-L1493
>
>
>
>
> On Tue, Aug 11, 2020 at 9:00 AM Maximilian Michels  wrote:
>
>> We ran into problems setting event time timers per-element in the Python
>> SDK. Pipeline progress would stall.
>>
>> Turns out, although the Python SDK does not expose the timer output
>> timestamp feature to the user, it sets the timer output timestamp to the
>> current input timestamp of an element.
>>
>> This will lead to holding back the watermark until the timer fires (the
>> Flink Runner respects the timer output timestamp when advancing the
>> output watermark). We had set the fire timestamp to a timestamp so far
>> in the future, that pipeline progress would completely stall for
>> downstream transforms, due to the held back watermark.
>>
>> Considering that this feature is not even exposed to the user in the
>> Python SDK, I think we should set the default output timestamp to the
>> fire timestamp, and not to the input timestamp. This is also how timer
>> work in the Java SDK.
>>
>> Let me know what you think.
>>
>> -Max
>>
>> PR: https://github.com/apache/beam/pull/12531
>>
>

Re: Unsure why Warning shows up for unmodified file on Java PR

[Yichi Zhang]

It looks like quite a few java precommit runs timed out
on :sdks:java:io:rabbitmq:test

On Mon, Jun 29, 2020 at 5:57 PM Alex Amato  wrote:

> PR: https://github.com/apache/beam/pull/12083
>
> Java ("Run Java PreCommit") is failing -
> https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/12011/
>
> When I dug into the console log and found the error details:
> https://screenshot.googleplex.com/EJkhH9Bq8en
>
> *15:14:55* 
> /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_Commit/src/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryIO.java:709:
>  error: cannot find symbol*15:14:55*   public abstract static class 
> TypedRead extends PTransform> {
>
>
> I actually don't modify BigQuery.java in my PR
> , but I do modify other
> files in the same folder. PTransform looks like it is imported properly in
> that file as well.
>
> Thanks for taking a look, any ideas would be appreciated :)
>
>

Re: [ANNOUNCE] Beam 2.21.0 Released

[Yichi Zhang]

Great work. Thanks, Kyle!

On Fri, May 29, 2020 at 6:05 PM Ahmet Altay  wrote:

> Thank you, Kyle!
>
> On Fri, May 29, 2020 at 12:52 AM Ismaël Mejía  wrote:
>
>> Thanks Kyle for all the work and patience as a release manager for this
>> version.
>>
>> On Thu, May 28, 2020, 7:47 PM Udi Meiri  wrote:
>>
>>> Woohoo!
>>>
>>> On Thu, May 28, 2020 at 4:16 AM Kyle Weaver  wrote:
>>>
 The Apache Beam team is pleased
 to announce the release of version 2.21.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 bug fixes, features, and improvements detailed on
 the Beam blog: https://beam.apache.org/blog/beam-2.21.0/

 Thanks to everyone who contributed to this release, and we hope you
 enjoy
 using Beam 2.21.0.
 -- Kyle Weaver, on behalf of The Apache Beam team

Re: [ANNOUNCE] New committer: Robin Qiu

[Yichi Zhang]

Congrats Robin!

On Tue, May 19, 2020 at 8:56 AM Kamil Wasilewski <
kamil.wasilew...@polidea.com> wrote:

> Congrats!
>
> On Tue, May 19, 2020 at 5:33 PM Jan Lukavský  wrote:
>
>> Congrats Robin!
>> On 5/19/20 5:01 PM, Tyson Hamilton wrote:
>>
>> Congratulations!
>>
>> On Tue, May 19, 2020 at 6:10 AM Omar Ismail 
>> wrote:
>>
>>> Congrats!
>>>
>>> On Tue, May 19, 2020 at 5:00 AM Gleb Kanterov  wrote:
>>>
 Congratulations!

 On Tue, May 19, 2020 at 7:31 AM Aizhamal Nurmamat kyzy <
 aizha...@apache.org> wrote:

> Congratulations, Robin! Thank you for your contributions!
>
> On Mon, May 18, 2020, 7:18 PM Boyuan Zhang  wrote:
>
>> Congrats~~
>>
>> On Mon, May 18, 2020 at 7:17 PM Reza Rokni  wrote:
>>
>>> Congratulations!
>>>
>>> On Tue, May 19, 2020 at 10:06 AM Ahmet Altay 
>>> wrote:
>>>
 Hi everyone,

 Please join me and the rest of the Beam PMC in welcoming a new
 committer: Robin Qiu .

 Robin has been active in the community for close to 2 years, worked
 on HyperLogLog++ [1], SQL [2], improved documentation, and helped with
 releases(*).

 In consideration of his contributions, the Beam PMC trusts him with
 the responsibilities of a Beam committer [3].

 Thank you for your contributions Robin!

 -Ahmet, on behalf of the Apache Beam PMC

 [1]
 https://www.meetup.com/Zurich-Apache-Beam-Meetup/events/265529665/
 [2]
 https://www.meetup.com/Belgium-Apache-Beam-Meetup/events/264933301/
 [3] https://beam.apache.org/contribute/become-a-committer
 /#an-apache-beam-committer
 (*) And maybe he will be a release manager soon :)

 --
>>>
>>> Omar Ismail |  Technical Solutions Engineer |  omarism...@google.com |
>>>
>>

Re: Google Summer of Code 2020 [Accepted Proposal]

[Yichi Zhang]

Congrats!

On Tue, May 5, 2020 at 5:07 PM Rui Wang  wrote:

> Welcome!
>
>
> -Rui
>
> On Tue, May 5, 2020 at 1:58 PM Chamikara Jayalath 
> wrote:
>
>> Congrats!
>>
>> On Tue, May 5, 2020 at 1:34 PM Robert Bradshaw 
>> wrote:
>>
>>> Congratulations and welcome!
>>>
>>> On Tue, May 5, 2020 at 12:46 PM Ismaël Mejía  wrote:
>>> >
>>> > Hello Aldair,
>>> > You were added in JIRA as a contributor.
>>> > Welcome to the project!
>>> >
>>> > On Tue, May 5, 2020 at 8:59 PM Aldair Coronel Ruíz
>>> >  wrote:
>>> > >
>>> > > Hi everyone!
>>> > >
>>> > > I'm Aldair. My GSoC 2020 project proposal was accepted! It will be
>>> my first time working on an open-source project and I'm excited.  My goal
>>> is to add support for Azure Blobstore file system in Apache Beam Python
>>> SDK.  You can find my proposal here [1]
>>> > >
>>> > > Pablo Estrada and Ismaël Mejía are my mentors and I just want to say
>>> thank you in advance. :)
>>> > >
>>> > > If you have any comments or suggestions feel free to let me know.
>>> > >
>>> > > One more thing:  Can someone add me as a contributor for Beam's Jira
>>> issue tracker? My username is Aldair
>>> > >
>>> > > Thank you
>>> > >
>>> > > [1]
>>> https://docs.google.com/document/d/1iax7Rkxoe3dxsAdxLwc8bkFGM6axom0foOePyjKI-6Y/edit
>>> > > --
>>> > > Aldair Coronel Ruiz
>>> > >
>>>
>>

Re: Hello Beam Community!

[Yichi Zhang]

Welcome!

On Fri, Mar 13, 2020 at 9:40 AM Ahmet Altay  wrote:

> Welcome Brittany!
>
> On Thu, Mar 12, 2020 at 6:32 PM Brittany Hermann 
> wrote:
>
>> Hello Beam Community!
>>
>> My name is Brittany Hermann and I recently joined the Open Source team in
>> Data Analytics at Google. As a Program Manager, I will be focusing on
>> community engagement while getting to work on Apache Beam and Airflow
>> projects! I have always thrived on creating healthy, diverse, and overall
>> happy communities and am excited to bring that to the team. For a fun fact,
>> I am a big Wisconsin Badgers Football fan and have a goldendoodle puppy
>> named Ollie!
>>
>> I look forward to collaborating with you all!
>>
>> Kind regards,
>>
>> Brittany Hermann
>>
>>
>>

Re: [ANNOUNCE] New Committer: Kamil Wasilewski

[Yichi Zhang]

Congrats, Kamil!

On Fri, Feb 28, 2020 at 9:53 AM Valentyn Tymofieiev 
wrote:

> Congratulations, Kamil!
>
> On Fri, Feb 28, 2020 at 9:34 AM Pablo Estrada  wrote:
>
>> Hi everyone,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new committer:
>> Kamil Wasilewski
>>
>> Kamil has contributed to Beam in many ways, including the performance
>> testing infrastructure, and a custom BQ source, along with other
>> contributions.
>>
>> In consideration of his contributions, the Beam PMC trusts him with the
>> responsibilities of a Beam committer[1].
>>
>> Thanks for your contributions Kamil!
>>
>> Pablo, on behalf of the Apache Beam PMC.
>>
>> [1] https://beam.apache.org/contribute/become-a-committer
>> /#an-apache-beam-committer
>>
>>

Re: [ANNOUNCE] New committer: Chad Dombrova

[Yichi Zhang]

Congratulations, Chad!

On Mon, Feb 24, 2020 at 3:10 PM Robert Bradshaw  wrote:

> Well deserved, Chad. Congratulations!
>
> On Mon, Feb 24, 2020 at 2:43 PM Reza Rokni  wrote:
> >
> > Congratulations! :-)
> >
> > On Tue, Feb 25, 2020 at 6:41 AM Chad Dombrova  wrote:
> >>
> >> Thanks, folks!  I'm very excited to "retest this" :)
> >>
> >> Especially big thanks to Robert and Udi for all their hard work
> reviewing my PRs.
> >>
> >> -chad
> >>
> >>
> >> On Mon, Feb 24, 2020 at 1:44 PM Brian Hulette 
> wrote:
> >>>
> >>> Congratulations Chad! Thanks for all your contributions :)
> >>>
> >>> On Mon, Feb 24, 2020 at 1:43 PM Kyle Weaver 
> wrote:
> 
>  Well-deserved, thanks for your dedication to the project Chad. :)
> 
>  On Mon, Feb 24, 2020 at 1:34 PM Udi Meiri  wrote:
> >
> > Congrats and welcome, Chad!
> >
> > On Mon, Feb 24, 2020 at 1:21 PM Pablo Estrada 
> wrote:
> >>
> >> Hi everyone,
> >>
> >> Please join me and the rest of the Beam PMC in welcoming a new
> committer: Chad Dombrova
> >>
> >> Chad has contributed to the project in multiple ways, including
> improvements to the testing infrastructure, and adding type annotations
> throughout the Python SDK, as well as working closely with the community on
> these improvements.
> >>
> >> In consideration of his contributions, the Beam PMC trusts him with
> the responsibilities of a Beam Committer[1].
> >>
> >> Thanks Chad for your contributions!
> >>
> >> -Pablo, on behalf of the Apache Beam PMC.
> >>
> >> [1]
> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>

Re: [ANNOUNCE] New committer: Jincheng Sun

[Yichi Zhang]

Congrats, Jincheng!

On Mon, Feb 24, 2020 at 9:45 AM Ahmet Altay  wrote:

> Congratulations!
>
> On Mon, Feb 24, 2020 at 6:48 AM Thomas Weise  wrote:
>
>> Congratulations!
>>
>>
>> On Mon, Feb 24, 2020 at 6:45 AM Ismaël Mejía  wrote:
>>
>>> Congrats Jincheng!
>>>
>>> On Mon, Feb 24, 2020 at 1:39 PM Gleb Kanterov  wrote:
>>>
 Congratulations!

 On Mon, Feb 24, 2020 at 1:18 PM Hequn Cheng  wrote:

> Congratulations Jincheng, well deserved!
>
> Best,
> Hequn
>
> On Mon, Feb 24, 2020 at 7:21 PM Reza Rokni  wrote:
>
>> Congrats!
>>
>> On Mon, Feb 24, 2020 at 7:15 PM Jan Lukavský  wrote:
>>
>>> Congrats Jincheng!
>>>
>>>   Jan
>>>
>>> On 2/24/20 11:55 AM, Maximilian Michels wrote:
>>> > Hi everyone,
>>> >
>>> > Please join me and the rest of the Beam PMC in welcoming a new
>>> > committer: Jincheng Sun 
>>> >
>>> > Jincheng has worked on generalizing parts of Beam for Flink's
>>> Python
>>> > API. He has also picked up other issues, like fixing
>>> documentation,
>>> > implementing missing features, or cleaning up code [1].
>>> >
>>> > In consideration of his contributions, the Beam PMC trusts him
>>> with
>>> > the responsibilities of a Beam committer [2].
>>> >
>>> > Thank you for your contributions Jincheng!
>>> >
>>> > -Max, on behalf of the Apache Beam PMC
>>> >
>>> > [1]
>>> >
>>> https://jira.apache.org/jira/browse/BEAM-9299?jql=project%20%3D%20BEAM%20AND%20assignee%20in%20(sunjincheng121)
>>> > [2]
>>> >
>>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>
>>

Re: [RELEASE VOTE RESULT] Release 2.19.0, release candidate #1

[Yichi Zhang]

Thanks, Boyuan!

On Mon, Feb 3, 2020 at 5:14 PM Ankur Goenka  wrote:

> Thanks Boyuan!
> A record has been set :)
>
> On Mon, Feb 3, 2020 at 5:05 PM Udi Meiri  wrote:
>
>> Thank you Boyuan!
>>
>> On Mon, Feb 3, 2020 at 3:40 PM Ahmet Altay  wrote:
>>
>>> On Mon, Feb 3, 2020 at 1:22 PM Thomas Weise  wrote:
>>>
 Impressive, probably the fastest/smoothest Beam release so far.

>>>
>>> I agree! Thank you, Boyuan!
>>>
>>>

 On Mon, Feb 3, 2020 at 10:45 AM Boyuan Zhang 
 wrote:

> I'm happy to announce that we have unanimously approved this release.
>
> There are 5 approving votes, 4 of which are binging:
> * Ahmet Altay
> * Ismaël Mejía
> * Jean-Baptiste Onofré
> * Robert Bradshaw
>
> There are no disapproving votes.
>
> Thanks for everyone's help! I'm going to finalize the release and send
> out the official release announcement later.
>

Re: [ANNOUNCE] New committer: Hannah Jiang

[Yichi Zhang]

Congrats Hannah!

On Tue, Jan 28, 2020 at 3:57 PM Yifan Zou  wrote:

> Congratulations Hannah!!
>
> On Tue, Jan 28, 2020 at 3:55 PM Boyuan Zhang  wrote:
>
>> Thanks for all your contributions! Congratulations~
>>
>> On Tue, Jan 28, 2020 at 3:44 PM Pablo Estrada  wrote:
>>
>>> yoooho : D
>>>
>>> On Tue, Jan 28, 2020 at 3:21 PM Luke Cwik  wrote:
>>>
 Hi everyone,

 Please join me and the rest of the Beam PMC in welcoming a new
 committer: Hannah Jiang

 Hannah has contributed to Beam in many ways, including work on building
 and releasing the Apache Beam SDK containers.

 In consideration of their contributions, the Beam PMC trusts them with
 the responsibilities of a Beam committer[1].

 Thanks for your contributions Hannah!

 Luke, on behalf of the Apache Beam PMC.

 [1]
 https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer

>>>

Re: [ANNOUNCE] Beam 2.18.0 Released

[Yichi Zhang]

Thanks Udi!

On Tue, Jan 28, 2020 at 11:28 AM Hannah Jiang 
wrote:

> Thanks Udi!
>
>
> On Tue, Jan 28, 2020 at 11:09 AM Pablo Estrada  wrote:
>
>> Thanks Udi!
>>
>> On Tue, Jan 28, 2020 at 11:08 AM Rui Wang  wrote:
>>
>>> Thank you Udi for taking care of Beam 2.18.0 release!
>>>
>>>
>>>
>>> -Rui
>>>
>>> On Tue, Jan 28, 2020 at 10:59 AM Udi Meiri  wrote:
>>>
 The Apache Beam team is pleased to announce the release of
 version 2.18.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 bug fixes, features, and improvements detailed on
 the Beam blog: https://beam.apache.org/blog/2020/01/13/beam-2.18.0.html

 Thanks to everyone who contributed to this release, and we hope you
 enjoy
 using Beam 2.18.0.
 -- Udi Meiri, on behalf of The Apache Beam team

>>>

Re: [DISCUSS] Autoformat python code with Black

[Yichi Zhang]

+1 to yapf, I normally run yapf before submitting PR and it seems to be
able to solve most of my lint errors (indentations most of the time) with
the correct style file.
it will be great if yapf has an option to only autoformat the diff change,
but seems not officially supported. (I use a vim format-selected plugin
with yapf to avoid formatting the whole file, but it is annoying since not
fully automated)
https://github.com/google/yapf/issues/190 seems relevant.

On Tue, Jan 21, 2020 at 12:52 PM Ismaël Mejía  wrote:

> Last time we discussed this there seems not to be much progress into
> autoformatting.
> This tool looks more tweakable, so maybe it could be more appropriate for
> Beam's use case.
> https://github.com/google/yapf/
> WDYT?
>
>
> On Thu, May 30, 2019 at 10:50 AM Łukasz Gajowy  wrote:
>
>> +1 for any autoformatter for Python SDK that does the job. My experience
>> is that since spotless in Java SDK I would never start a new Java project
>> without it. So many great benefits not only for one person coding but for
>> all community.
>>
>> It is a GitHub UI issue that you cannot easily browse past the reformat.
>> It is not actually that hard, but does take a couple extra clicks to get
>> GitHub to display blame before a reformat. It is easier with the command
>> line. I do a lot of code history digging and the global Java reformat is
>> not really a problem.
>>
>> It's actually one more click on Github but I agree it's not the best way
>> to search the history. The most convenient and clear one I've found so far
>> is in Jetbrains IDEs (Intelij) where you can:
>>
>> right click on line number -> "annotate" -> click again -> "annotate
>> previous revision" -> ...
>>
>> You can also use "compare with" to see the diff between two revisions.
>>
>> Łukasz
>>
>>
>>
>>
>>
>> czw., 30 maj 2019 o 06:15 Kenneth Knowles  napisał(a):
>>
>>> +1 pending good enough tooling (I can't quite tell - seems there are
>>> some issues?)
>>>
>>> On Wed, May 29, 2019 at 2:40 PM Katarzyna Kucharczyk <
>>> ka.kucharc...@gmail.com> wrote:
>>>
 What else actually we gain? My guess is faster PR review iteration. We
 will skip some of conversations about code style.

>>> ...
>>>
 Last but not least, new contributor may be less discouraged. When I
 started contribute I didn’t know how to format my code and I lost a lot of
 time to add pylint and adjust IntelliJ. I eventually failed. Currently I
 write code intuitively and when I don’t forget I rerun tox.

>>>
>>> This is a huge benefit. This is why I supported it so much for Java. It
>>> is a community benefit. You do not have to be a contributor to the Python
>>> SDK to support this. That is why I am writing here. Just eliminate all
>>> discussion of formatting. It doesn't really matter what the resulting
>>> format is, if it is not crazy to read. I strongly oppose maintaining a
>>> non-default format.
>>>
>>> Reformating 20k lines or 200k is not hard. The Java global reformat
>>> touched 50k lines. It does not really matter how big it is. Definitely do
>>> it all at once if you think the tool is good enough. And you should pin a
>>> version, so churn is not a problem. You can upgrade the version and
>>> reformat in a PR later and that is also easy.
>>>
>>> It is a GitHub UI issue that you cannot easily browse past the reformat.
>>> It is not actually that hard, but does take a couple extra clicks to get
>>> GitHub to display blame before a reformat. It is easier with the command
>>> line. I do a lot of code history digging and the global Java reformat is
>>> not really a problem.
>>>
>>> Kenn
>>>
>>>
>>>
 Also everything will be formatted in a same way, so eventually it would
 be easier to read.

 Moreover, as it was mentioned in previous emails - a lot of Jenkins
 failures won’t take place, so we save time and resources.


 One of disadvantages is that our pipelines has custom syntax and after
 formatting they looks a little bit weird, but maybe extending the only
 configurable option in Black - lines, from 88 to 110 would be solution.

 Second one is that Black requires Python 3 to be run. I don’t know how
 big obstacle it would be.

 I believe there are two options how it would be possible to introduce
 Black. First: just do it, it will hurt but then it would be ok (same as a
 dentist appointment). Of course it may require some work to adjust linters.
 On the other hand we can do it gradually and start including sdk parts one
 by one - maybe it will be less painful?

 As an example I can share one of projects [2] I know that uses Black
 (they use also other cool checkers and pre-commit [3]). This is how looks
 their build with all checks [4].

 To sum up I believe that if we want improve our coding experience, we
 should improve our toolset. Black seems be recent and quite popular tool
 what makes think they won’t stop developing it.

Re: [ANNOUNCE] Beam 2.17.0 Released!

[Yichi Zhang]

Thank you Mikahil!

On Fri, Jan 10, 2020 at 12:52 PM Ahmet Altay  wrote:

> Thank you Mikhail!
>
> On Fri, Jan 10, 2020 at 12:40 PM Kyle Weaver  wrote:
>
>> Hooray! Thanks to Mikhail and everyone else who contributed.
>>
>> On Fri, Jan 10, 2020 at 10:23 AM Maximilian Michels 
>> wrote:
>>
>>> At last :) Thank you for making it happen Mikhail! Also thanks to
>>> everyone else who tested the release candidate.
>>>
>>> Cheers,
>>> Max
>>>
>>> On 10.01.20 19:01, Mikhail Gryzykhin wrote:
>>> > The Apache Beam team is pleased to announce the release of version
>>> 2.17.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 bug fixes, features, and improvements detailed on
>>> > the Beam blog:
>>> https://beam.apache.org/blog/2020/01/06/beam-2.17.0.html
>>> > 
>>> >
>>> > Thanks to everyone who contributed to this release, and we hope you
>>> > enjoy using Beam 2.17.0.
>>>
>>

Re: [ANNOUNCE] New committer: Kasia Kucharczyk

[Yichi Zhang]

Congrats Kasia!

On Mon, Dec 23, 2019 at 2:07 PM Rui Wang  wrote:

> Congrats!
>
>
> -Rui
>
> On Mon, Dec 23, 2019 at 1:39 PM Udi Meiri  wrote:
>
>> Congrats Kasia!
>>
>> On Mon, Dec 23, 2019 at 1:23 PM Kyle Weaver  wrote:
>>
>>> Congrats Kasia! And thanks for sharing, Pablo.
>>>
>>> On Mon, Dec 23, 2019 at 4:16 PM Pablo Estrada 
>>> wrote:
>>>
 Hi everyone,

 Please join me and the rest of the Beam PMC in welcoming a new
 committer: Kasia Kucharczyk

 Kasia has contributed to Beam in many ways, including the performance
 testing infrastructure, and has even spoken at events about Beam.

 In consideration of Kasia's contributions, the Beam PMC trusts her with
 the responsibilities of a Beam committer[1].

 Thanks for your contributions Kasia!

 Pablo, on behalf of the Apache Beam PMC.

 [1] https://beam.apache.org/contribute/become-a-committer
 /#an-apache-beam-committer

>>>

Re: [ANNOUNCE] New committer: Daniel Oliveira

[Yichi Zhang]

Congrats, Daniel!

On Thu, Nov 21, 2019 at 9:53 AM Aizhamal Nurmamat kyzy 
wrote:

> Congratulations, Daniel!!!
>
> On Thu, Nov 21, 2019 at 2:17 AM Connell O'Callaghan 
> wrote:
>
>> Well done - congratulations Daniel!!!
>> Kenn thank you for sharing!!!
>>
>> On Thu, Nov 21, 2019 at 1:32 AM Robin Qiu  wrote:
>>
>>> Congrats, Daniel!
>>>
>>> On Thu, Nov 21, 2019 at 10:11 AM Gleb Kanterov  wrote:
>>>
 Congratulations!

 On Thu, Nov 21, 2019 at 6:24 AM Thomas Weise  wrote:

> Congratulations!
>
>
> On Wed, Nov 20, 2019, 7:56 PM Chamikara Jayalath 
> wrote:
>
>> Congrats!!
>>
>> On Wed, Nov 20, 2019 at 5:21 PM Daniel Oliveira <
>> danolive...@google.com> wrote:
>>
>>> Thank you everyone! I won't let you down. o7
>>>
>>> On Wed, Nov 20, 2019 at 2:12 PM Ruoyun Huang 
>>> wrote:
>>>
 Congrats Daniel!

 On Wed, Nov 20, 2019 at 1:58 PM Robert Burke 
 wrote:

> Congrats Daniel! Much deserved.
>
> On Wed, Nov 20, 2019, 12:49 PM Udi Meiri  wrote:
>
>> Congrats Daniel!
>>
>> On Wed, Nov 20, 2019 at 12:42 PM Kyle Weaver 
>> wrote:
>>
>>> Congrats Dan! Keep up the good work :)
>>>
>>> On Wed, Nov 20, 2019 at 12:41 PM Cyrus Maden 
>>> wrote:
>>>
 Congratulations! This is great news.

 On Wed, Nov 20, 2019 at 3:24 PM Rui Wang 
 wrote:

> Congrats!
>
>
> -Rui
>
> On Wed, Nov 20, 2019 at 11:48 AM Valentyn Tymofieiev <
> valen...@google.com> wrote:
>
>> Congrats, Daniel!
>>
>> On Wed, Nov 20, 2019 at 11:47 AM Kenneth Knowles <
>> k...@apache.org> wrote:
>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a
>>> new committer: Daniel Oliveira
>>>
>>> Daniel introduced himself to dev@ over two years ago and
>>> has contributed in many ways since then. Daniel has contributed 
>>> to general
>>> project health, the portability framework, and all three 
>>> languages: Java,
>>> Python SDK, and Go. I would like to particularly highlight how 
>>> he deleted
>>> 12k lines of dead reference runner code [1].
>>>
>>> In consideration of Daniel's contributions, the Beam PMC
>>> trusts him with the responsibilities of a Beam committer [2].
>>>
>>> Thank you, Daniel, for your contributions and looking
>>> forward to many more!
>>>
>>> Kenn, on behalf of the Apache Beam PMC
>>>
>>> [1] https://github.com/apache/beam/pull/8380
>>> [2]
>>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>
>>

 --
 
 Ruoyun  Huang

Re: [ANNOUNCE] New committer: Brian Hulette

[Yichi Zhang]

Congratulations, Brian!

On Fri, Nov 15, 2019 at 11:12 AM Alan Myrvold  wrote:

> Congratulations, Brian!
>
> On Fri, Nov 15, 2019 at 11:11 AM Yifan Zou  wrote:
>
>> Well deserved. Congratulations!
>>
>> On Fri, Nov 15, 2019 at 11:06 AM Kirill Kozlov 
>> wrote:
>>
>>> Congratulations, Brian!
>>>
>>> On Fri, Nov 15, 2019 at 10:56 AM Udi Meiri  wrote:
>>>
 Congrats Brian!


 On Fri, Nov 15, 2019 at 10:47 AM Ruoyun Huang 
 wrote:

> Congrats Brian!
>
> On Fri, Nov 15, 2019 at 10:41 AM Robin Qiu  wrote:
>
>> Congrats, Brian!
>>
>> On Fri, Nov 15, 2019 at 10:02 AM Daniel Oliveira <
>> danolive...@google.com> wrote:
>>
>>> Congratulations Brian! It's well deserved.
>>>
>>> On Fri, Nov 15, 2019, 9:37 AM Alexey Romanenko <
>>> aromanenko@gmail.com> wrote:
>>>
 Congratulations, Brian!

 On 15 Nov 2019, at 18:27, Rui Wang  wrote:

 Congrats!


 -Rui

 On Fri, Nov 15, 2019 at 8:16 AM Thomas Weise 
 wrote:

> Congratulations!
>
>
> On Fri, Nov 15, 2019 at 6:34 AM Connell O'Callaghan <
> conne...@google.com> wrote:
>
>> Well done Brian!!!
>>
>> Kenn thank you for sharing
>>
>> On Fri, Nov 15, 2019 at 6:31 AM Cyrus Maden 
>> wrote:
>>
>>> Congrats Brian!
>>>
>>> On Fri, Nov 15, 2019 at 5:25 AM Ismaël Mejía 
>>> wrote:
>>>
 Congratulations Brian!
 Happy to see this happening and eager to see more of your work!

 On Fri, Nov 15, 2019 at 11:02 AM Ankur Goenka <
 goe...@google.com> wrote:
 >
 > Congrats Brian!
 >
 > On Fri, Nov 15, 2019, 2:42 PM Jan Lukavský 
 wrote:
 >>
 >> Congrats Brian!
 >>
 >> On 11/15/19 9:58 AM, Reza Rokni wrote:
 >>
 >> Great news!
 >>
 >> On Fri, 15 Nov 2019 at 15:09, Gleb Kanterov <
 g...@spotify.com> wrote:
 >>>
 >>> Congratulations!
 >>>
 >>> On Fri, Nov 15, 2019 at 5:44 AM Valentyn Tymofieiev <
 valen...@google.com> wrote:
 
  Congratulations, Brian!
 
  On Thu, Nov 14, 2019 at 6:25 PM jincheng sun <
 sunjincheng...@gmail.com> wrote:
 >
 > Congratulation Brian!
 >
 > Best,
 > Jincheng
 >
 > Kyle Weaver  于2019年11月15日周五
 上午7:19写道：
 >>
 >> Thanks for your contributions and congrats Brian!
 >>
 >> On Thu, Nov 14, 2019 at 3:14 PM Kenneth Knowles <
 k...@apache.org> wrote:
 >>>
 >>> Hi all,
 >>>
 >>> Please join me and the rest of the Beam PMC in
 welcoming a new committer: Brian Hulette
 >>>
 >>> Brian introduced himself to dev@ earlier this year and
 has been contributing since then. His contributions to Beam include
 explorations of integration with Arrow, standardizing coders, 
 portability
 for schemas, and presentations at Beam events.
 >>>
 >>> In consideration of Brian's contributions, the Beam PMC
 trusts him with the responsibilities of a Beam committer [1].
 >>>
 >>> Thank you, Brian, for your contributions and looking
 forward to many more!
 >>>
 >>> Kenn, on behalf of the Apache Beam PMC
 >>>
 >>> [1]
 https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
 >>
 >>
 >>
 >> --
 >>
 >> This email may be confidential and privileged. If you
 received this communication by mistake, please don't forward it to 
 anyone
 else, please erase all copies and attachments, and please let me 
 know that
 it has gone to the wrong person.
 >>
 >> The above terms reflect a potential business arrangement,
 are provided solely as a basis for further discussion, and are not 
 intended
 to be and do not constitute a legally binding obligation. No 
 legally
 binding obligations will be created, implied, or inferred until an
 agreement in final form is executed in writing by all parties 
 involved.

>>>

>
> --
> ===

[discuss] Exposing sdk harness status to runner for better debuggability

[Yichi Zhang]

Hi, beam dev community,

After seeing some difficulties in troubleshooting python pipelines in
Dataflow, we came up with an idea to expose sdk harness status to runners
through Fn API for better debuggability.

I put up a doc describing the background and proposed approach:

https://docs.google.com/document/d/1W77buQtdSEIPUKd9zemAM38fb-x3CvOoaTF4P2mSxmI/edit?usp=sharing

Feedbacks are very much appreciated.

Thanks,
Yichi

Re: [ANNOUNCE] New committer: Alan Myrvold

[Yichi Zhang]

Congrats, Alan!

On Fri, Sep 27, 2019 at 10:26 AM Robin Qiu  wrote:

> Congrats, Alan!
>
> On Fri, Sep 27, 2019 at 10:15 AM Hannah Jiang 
> wrote:
>
>> Congrats Alan!
>>
>> On Fri, Sep 27, 2019 at 9:57 AM Ruoyun Huang  wrote:
>>
>>> Congratulations, Alan!
>>>
>>>
>>> On Fri, Sep 27, 2019 at 9:55 AM Rui Wang  wrote:
>>>
 Congrats!

 -Rui

 On Fri, Sep 27, 2019 at 9:54 AM Pablo Estrada 
 wrote:

> Yooh! : D
>
> On Fri, Sep 27, 2019 at 9:53 AM Yifan Zou  wrote:
>
>> Congratulations, Alan!
>>
>> On Fri, Sep 27, 2019 at 9:18 AM Ahmet Altay  wrote:
>>
>>> Hi,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new
>>> committer: Alan Myrvold
>>>
>>> Alan has been a long time Beam contributor. His contributions made
>>> Beam more productive and friendlier [1] for all contributors with
>>> significant improvements to Beam release process, automation, and
>>> infrastructure.
>>>
>>> In consideration of Alan's contributions, the Beam PMC trusts him
>>> with the responsibilities of a Beam committer [2].
>>>
>>> Thank you, Alan, for your contributions and looking forward to many
>>> more!
>>>
>>> Ahmet, on behalf of the Apache Beam PMC
>>>
>>> [1]
>>> https://beam-summit-na-2019.firebaseapp.com/schedule/2019-09-11?sessionId=1126
>>> [2] https://beam.apache.org/contribute/become-a-committer
>>> /#an-apache-beam-committer
>>>
>>
>>>
>>> --
>>> 
>>> Ruoyun  Huang
>>>
>>>

Re: [ANNOUNCE] New committer: Valentyn Tymofieiev

[Yichi Zhang]

Congrats Valentyn!

On Tue, Aug 27, 2019 at 7:55 AM Valentyn Tymofieiev 
wrote:

> Thank you everyone!
>
> On Tue, Aug 27, 2019 at 2:57 AM Alexey Romanenko 
> wrote:
>
>> Congrats, well deserved!
>>
>> On 27 Aug 2019, at 11:25, Jan Lukavský  wrote:
>>
>> Congrats Valentyn!
>> On 8/26/19 11:43 PM, Rui Wang wrote:
>>
>> Congratulations!
>>
>>
>> -Rui
>>
>> On Mon, Aug 26, 2019 at 2:36 PM Hannah Jiang 
>> wrote:
>>
>>> Congratulations Valentyn, well deserved!
>>>
>>> On Mon, Aug 26, 2019 at 2:34 PM Chamikara Jayalath 
>>> wrote:
>>>
 Congrats Valentyn!

 On Mon, Aug 26, 2019 at 2:32 PM Pablo Estrada 
 wrote:

> Thanks Valentyn!
>
> On Mon, Aug 26, 2019 at 2:29 PM Robin Qiu  wrote:
>
>> Thank you Valentyn! Congratulations!
>>
>> On Mon, Aug 26, 2019 at 2:28 PM Robert Bradshaw 
>> wrote:
>>
>>> Hi,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new
>>> committer: Valentyn Tymofieiev
>>>
>>> Valentyn has made numerous contributions to Beam over the last
>>> several
>>> years (including 100+ pull requests), most recently pushing through
>>> the effort to make Beam compatible with Python 3. He is also an
>>> active
>>> participant in design discussions on the list, participates in
>>> release
>>> candidate validation, and proactively helps keep our tests green.
>>>
>>> In consideration of Valentyn's contributions, the Beam PMC trusts him
>>> with the responsibilities of a Beam committer [1].
>>>
>>> Thank you, Valentyn, for your contributions and looking forward to
>>> many more!
>>>
>>> Robert, on behalf of the Apache Beam PMC
>>>
>>> [1]
>>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>
>>
>>

Re: [ANNOUNCE] Beam 2.15.0 Released!

[Yichi Zhang]

Thank you Yifan!

On Fri, Aug 23, 2019 at 11:06 AM Robin Qiu  wrote:

> Thank you Yifan!
>
> On Fri, Aug 23, 2019 at 11:05 AM Rui Wang  wrote:
>
>> Thank you Yifan!
>>
>> -Rui
>>
>> On Fri, Aug 23, 2019 at 9:21 AM Pablo Estrada  wrote:
>>
>>> Thanks Yifan!
>>>
>>> On Fri, Aug 23, 2019 at 8:54 AM Connell O'Callaghan 
>>> wrote:
>>>

 +1 thank you Yifan!!!

 On Fri, Aug 23, 2019 at 8:49 AM Ahmet Altay  wrote:

> Thank you Yifan!
>
> On Fri, Aug 23, 2019 at 8:00 AM Yifan Zou  wrote:
>
>> The Apache Beam team is pleased to announce the release of version
>> 2.15.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 bug fixes, features, and improvements detailed
>> on
>> the Beam blog:
>> https://beam.apache.org/blog/2019/08/22/beam-2.15.0.html
>>
>> Thanks to everyone who contributed to this release, and we hope you
>> enjoy
>> using Beam 2.15.0.
>>
>> Yifan Zou
>>
>

Re: [ANNOUNCE] New committer: Rui Wang

[Yichi Zhang]

Congrats Rui!

On Tue, Aug 6, 2019 at 1:29 PM Aizhamal Nurmamat kyzy 
wrote:

> Congratulations, Rui! Thank you for your contributions to Beam!
>
> On Tue, Aug 6, 2019 at 10:35 AM sridhar inuog 
> wrote:
>
>> Congratulations Rui!
>>
>> On Tue, Aug 6, 2019 at 12:09 PM Hannah Jiang 
>> wrote:
>>
>>> Congrats Rui!
>>>
>>> On Tue, Aug 6, 2019 at 9:50 AM Yifan Zou  wrote:
>>>
 Congratulations Rui!

 On Tue, Aug 6, 2019 at 9:47 AM Anton Kedin  wrote:

> Congrats!
>
> On Tue, Aug 6, 2019, 9:36 AM Ankur Goenka  wrote:
>
>> Congratulations Rui!
>> Well deserved 👏
>>
>> On Tue, Aug 6, 2019 at 9:35 AM Ahmet Altay  wrote:
>>
>>> Hi,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new
>>> committer: Rui Wang.
>>>
>>> Rui has been an active contributor since May 2018. Rui has been very
>>> active in Beam SQL [1] and continues to help out on user@ and
>>> StackOverflow. Rui is one of the top answerers for apache-beam tag [2].
>>>
>>> In consideration of Rui's contributions, the Beam PMC trusts him
>>> with the responsibilities of a Beam committer [3].
>>>
>>> Thank you, Rui, for your contributions and looking forward to many
>>> more!
>>>
>>> Ahmet, on behalf of the Apache Beam PMC
>>>
>>> [1]
>>> https://github.com/apache/beam/pulls?q=is%3Apr+author%3Aamaliujia
>>> [2] https://stackoverflow.com/tags/apache-beam/topusers
>>> [3] https://beam.apache.org/contribute/become-a-committer
>>> /#an-apache-beam-committer
>>>
>>

Re: [ANNOUNCE] New committer: Kyle Weaver

[Yichi Zhang]

Congrats Kyle!

On Tue, Aug 6, 2019 at 1:29 PM Aizhamal Nurmamat kyzy 
wrote:

> Thank you, Kyle! And congratulations :)
>
> On Tue, Aug 6, 2019 at 10:09 AM Hannah Jiang 
> wrote:
>
>> Congrats Kyle!
>>
>> On Tue, Aug 6, 2019 at 9:52 AM David Morávek 
>> wrote:
>>
>>> Congratulations Kyle!!
>>>
>>> Sent from my iPhone
>>>
>>> On 6 Aug 2019, at 18:47, Anton Kedin  wrote:
>>>
>>> Congrats!
>>>
>>> On Tue, Aug 6, 2019, 9:37 AM Ankur Goenka  wrote:
>>>
 Congratulations Kyle!

 On Tue, Aug 6, 2019 at 9:35 AM Ahmet Altay  wrote:

> Hi,
>
> Please join me and the rest of the Beam PMC in welcoming a new
> committer: Kyle Weaver.
>
> Kyle has been contributing to Beam for a while now. And in that time
> period Kyle got the portable spark runner feature complete for batch
> processing. [1]
>
> In consideration of Kyle's contributions, the Beam PMC trusts him with
> the responsibilities of a Beam committer [2].
>
> Thank you, Kyle, for your contributions and looking forward to many
> more!
>
> Ahmet, on behalf of the Apache Beam PMC
>
> [1]
> https://lists.apache.org/thread.html/c43678fc24c9a1dc9f48c51c51950aedcb9bc0fd3b633df16c3d595a@%3Cuser.beam.apache.org%3E
> [2] https://beam.apache.org/contribute/become-a-committer
> /#an-apache-beam-committer
>

Re: [ANNOUNCE] New committer: Robert Burke

[Yichi Zhang]

Congratulations!

On Tue, Jul 16, 2019 at 10:51 AM Holden Karau  wrote:

> Congratulations! :)
>
> On Tue, Jul 16, 2019 at 10:50 AM Mikhail Gryzykhin 
> wrote:
>
>> Congratulations!
>>
>> On Tue, Jul 16, 2019 at 10:36 AM Ankur Goenka  wrote:
>>
>>> Congratulations Robert!
>>>
>>> Go GO!
>>>
>>> On Tue, Jul 16, 2019 at 10:34 AM Rui Wang  wrote:
>>>
 Congrats!


 -Rui

 On Tue, Jul 16, 2019 at 10:32 AM Udi Meiri  wrote:

> Congrats Robert B.!
>
> On Tue, Jul 16, 2019 at 10:23 AM Ahmet Altay  wrote:
>
>> Hi,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new
>> committer: Robert Burke.
>>
>> Robert has been contributing to Beam and actively involved in the
>> community for over a year. He has been actively working on Go SDK, 
>> helping
>> users, and making it easier for others to contribute [1].
>>
>> In consideration of Robert's contributions, the Beam PMC trusts him
>> with the responsibilities of a Beam committer [2].
>>
>> Thank you, Robert, for your contributions and looking forward to many
>> more!
>>
>> Ahmet, on behalf of the Apache Beam PMC
>>
>> [1]
>> https://lists.apache.org/thread.html/8f729da2d3009059d7a8b2d8624446be161700dcfa953939dd3530c6@%3Cdev.beam.apache.org%3E
>> [2] https://beam.apache.org/contribute/become-a-committer
>> /#an-apache-beam-committer
>>
>
>
> --
> Twitter: https://twitter.com/holdenkarau
> Books (Learning Spark, High Performance Spark, etc.):
> https://amzn.to/2MaRAG9  
> YouTube Live Streams: https://www.youtube.com/user/holdenkarau
>

Re: Live fixing of a Beam bug on July 25 at 3:30pm-4:30pm PST

[Yichi Zhang]

Thanks for organizing this Pablo, it'll be very helpful!

On Tue, Jul 16, 2019 at 10:57 AM Pablo Estrada  wrote:

> Hello all,
> I'll be having a session where I live-fix a Beam bug for 1 hour next week.
> Everyone is invited.
>
> It will be on July 25, between 3:30pm and 4:30pm PST. Hopefully I will
> finish a full change in that time frame, but we'll see.
>
> I have not yet decided if I will do this via hangouts, or via a youtube
> livestream. In any case, I will share the link here in the next few days.
>
> I will most likely work on the Java SDK (I have a little feature request
> in mind).
>
> Thanks!
> -P.
>

Re: apache-beam-jenkins-15 out of disk

[Yichi Zhang]

for flakiness I guess a tag is needed to separate concurrent build apart.

On Thu, Jun 27, 2019 at 8:39 PM Yichi Zhang  wrote:

> maybe a cron job on jenkins node that does docker prune every day?
>
> On Thu, Jun 27, 2019 at 6:58 PM Ankur Goenka  wrote:
>
>> This highlights the race condition caused by using single docker registry
>> on a machine.
>> If 2 tests create "jenkins-docker-apache.bintray.io/beam/python" one
>> after another then the 2nd one will replace the 1st one and cause flakyness.
>>
>> Is their a way to dynamically create and destroy docker repository on a
>> machine and clean all the relevant data?
>>
>> On Thu, Jun 27, 2019 at 3:15 PM Yifan Zou  wrote:
>>
>>> The problem was because of the large quantity of stale docker images
>>> generated by the Python portable tests and HDFS IT.
>>>
>>> Dumping the docker disk usage gives me:
>>>
>>> TYPETOTAL   ACTIVE  SIZE
>>>RECLAIMABLE
>>> *Images  1039356 424GB
>>> 384.2GB (90%)*
>>> Containers  987 2   2.042GB
>>> 2.041GB (99%)
>>> Local Volumes   126 0   392.8MB
>>> 392.8MB (100%)
>>>
>>> REPOSITORY
>>>   TAG IMAGE IDCREATED
>>> SIZESHARED SIZE UNIQUE SIZE CONTAINERS
>>> jenkins-docker-apache.bintray.io/beam/python3
>>>  latest  ff1b949f444222 hours ago1.639GB
>>>   922.3MB  716.9MB 0
>>> jenkins-docker-apache.bintray.io/beam/python
>>>  latest  1dda7b9d974822 hours ago1.624GB
>>>   913.7MB   710.3MB 0
>>> 
>>>05458187a0e322 hours ago
>>>  732.9MB 625.1MB107.8MB 4
>>> 
>>>896f35dd685f23 hours ago
>>>  1.639GB 922.3MB   716.9MB 0
>>> 
>>>db4d24ca9f2b23 hours ago
>>>  1.624GB 913.7MB  710.3MB 0
>>> 
>>>   547df4d71c3123 hours ago
>>>  732.9MB 625.1MB 107.8MB 4
>>> 
>>>   dd7d9582c3e023 hours ago
>>>  1.639GB 922.3MB 716.9MB 0
>>> 
>>>   664aae25523923 hours ago
>>>  1.624GB 913.7MB 710.3MB 0
>>> 
>>> b528fedf922823 hours ago
>>>732.9MB 625.1MB 107.8MB 4
>>> 
>>> 8e996f22435e25 hours ago
>>>1.624GB 913.7MB710.3MB 0
>>> hdfs_it-jenkins-beam_postcommit_python_verify_pr-818_testlatest
>>>  24b73b3fec0625 hours ago1.305GB
>>> 965.7MB   339.5MB 0
>>> 
>>> 096325fb48de   25 hours ago
>>>  732.9MB 625.1MB107.8MB  2
>>> jenkins-docker-apache.bintray.io/beam/java
>>>  latest  c36d8ff2945d  25 hours ago685.6MB
>>> 625.1MB   60.52MB 0
>>> 
>>>   11c86ebe025f26 hours ago
>>>  1.639GB 922.3MB  716.9MB 0
>>> 
>>>   2ecd69c89ec126 hours ago
>>>  1.624GB 913.7MB 710.3MB 0
>>> hdfs_it-jenkins-beam_postcommit_python_verify-8590_testlatest
>>>3d1d589d44fe2 days ago  1.305GB
>>> 965.7MB   339.5MB 0
>>> hdfs_it-jenkins-beam_postcommit_python_verify_pr-801_test  latest
>>>d1cc503ebe8e2 days ago  1.305GB
>>> 965.7MB 339.2MB 0
>>> hdfs_it-jenkins-beam_postcommit_python_verify-8577_testlatest
>>>8582c6ca6e153 days ago  1.305GB
>>> 965.7MB   

Re: apache-beam-jenkins-15 out of disk

[Yichi Zhang]

maybe a cron job on jenkins node that does docker prune every day?

On Thu, Jun 27, 2019 at 6:58 PM Ankur Goenka  wrote:

> This highlights the race condition caused by using single docker registry
> on a machine.
> If 2 tests create "jenkins-docker-apache.bintray.io/beam/python" one
> after another then the 2nd one will replace the 1st one and cause flakyness.
>
> Is their a way to dynamically create and destroy docker repository on a
> machine and clean all the relevant data?
>
> On Thu, Jun 27, 2019 at 3:15 PM Yifan Zou  wrote:
>
>> The problem was because of the large quantity of stale docker images
>> generated by the Python portable tests and HDFS IT.
>>
>> Dumping the docker disk usage gives me:
>>
>> TYPETOTAL   ACTIVE  SIZE
>>RECLAIMABLE
>> *Images  1039356 424GB
>> 384.2GB (90%)*
>> Containers  987 2   2.042GB
>>   2.041GB (99%)
>> Local Volumes   126 0   392.8MB
>>   392.8MB (100%)
>>
>> REPOSITORY
>> TAG IMAGE IDCREATED
>> SIZESHARED SIZE UNIQUE SIZE CONTAINERS
>> jenkins-docker-apache.bintray.io/beam/python3
>>  latest  ff1b949f444222 hours ago1.639GB
>>   922.3MB  716.9MB 0
>> jenkins-docker-apache.bintray.io/beam/python
>>  latest  1dda7b9d974822 hours ago1.624GB
>>   913.7MB   710.3MB 0
>> 
>>  05458187a0e322 hours ago
>>732.9MB 625.1MB107.8MB 4
>> 
>>  896f35dd685f23 hours ago
>>1.639GB 922.3MB   716.9MB 0
>> 
>>  db4d24ca9f2b23 hours ago
>>1.624GB 913.7MB  710.3MB 0
>> 
>>   547df4d71c3123 hours ago
>>  732.9MB 625.1MB 107.8MB 4
>> 
>>   dd7d9582c3e023 hours ago
>>  1.639GB 922.3MB 716.9MB 0
>> 
>>   664aae25523923 hours ago
>>  1.624GB 913.7MB 710.3MB 0
>> 
>>   b528fedf922823 hours ago
>>  732.9MB 625.1MB 107.8MB 4
>> 
>>   8e996f22435e25 hours ago
>>  1.624GB 913.7MB710.3MB 0
>> hdfs_it-jenkins-beam_postcommit_python_verify_pr-818_testlatest
>>24b73b3fec0625 hours ago1.305GB 965.7MB
>>  339.5MB 0
>> 
>>   096325fb48de   25 hours ago
>>732.9MB 625.1MB107.8MB  2
>> jenkins-docker-apache.bintray.io/beam/java
>>  latest  c36d8ff2945d  25 hours ago685.6MB
>> 625.1MB   60.52MB 0
>> 
>>   11c86ebe025f26 hours ago
>>  1.639GB 922.3MB  716.9MB 0
>> 
>>   2ecd69c89ec126 hours ago
>>  1.624GB 913.7MB 710.3MB 0
>> hdfs_it-jenkins-beam_postcommit_python_verify-8590_testlatest
>>  3d1d589d44fe2 days ago  1.305GB
>> 965.7MB   339.5MB 0
>> hdfs_it-jenkins-beam_postcommit_python_verify_pr-801_test  latest
>>  d1cc503ebe8e2 days ago  1.305GB
>> 965.7MB 339.2MB 0
>> hdfs_it-jenkins-beam_postcommit_python_verify-8577_testlatest
>>  8582c6ca6e153 days ago  1.305GB
>> 965.7MB  339.2MB 0
>> hdfs_it-jenkins-beam_postcommit_python_verify-8576_testlatest
>>  4591e09481703 days ago  1.305GB
>> 965.7MB  339.2MB 0
>> hdfs_it-jenkins-beam_postcommit_python_verify-8575_testlatest
>>  ab181c49d56e4 days ago  1.305GB
>> 965.7MB  339.2MB 0
>> hdfs_it-jenkins-beam_postcommit_python_verify-8573_testlatest
>>  2104ba0a6db74 days ago  1.305GB
>> 965.7MB  339.2MB 0
>> ...
>> <1000+ images>
>>
>> I removed unused the images and the beam15 is back now.
>>
>> Opened https://issues.apache.org/jira/browse/BEAM-7650.
>> Ankur, I assigned the issue to you. Feel free to reassign it if needed.
>>
>> Thank you.
>> Yifan
>>
>> On Thu, Jun 27, 2019 at 11:29 AM Yifan Zou  wrote:
>>
>>> Something were eating the disk. Disconnected the worker so jobs could be
>>> allo

Re: Pull panda

[Yichi Zhang]

Add onto that I feel the codecov github integration might be valuable for
beam as can show code coverage on pull requests.
https://github.com/marketplace/codecov
https://codecov.io/

On Mon, Jun 24, 2019 at 3:01 AM Łukasz Gajowy  wrote:

> Hi all,
>
> I just came across this thing called Pull Panda [1], [2]. It's now
> available in Github marketplace for free. To me, the "Pull reminder"
> feature looks the most interesting form beam's perspective. Maybe it could
> mitigate some delays that we sometimes have in pull requests reviews. Pull
> assigner and analytics look interesting too but I'm not sure if we need
> this given that we have similar tools.
>
> What do you think about that tool? Should we integrate it (parts of it)
> with beam's repo?
>
> Thanks,
> Łukasz
>
> [1] https://pullpanda.com/
> [2] https://www.youtube.com/watch?time_continue=8&v=RtZdbZiPeK8 (tldr
> video)
>
>
>

Re: [ANNOUNCE] New committer: Mikhail Gryzykhin

[Yichi Zhang]

Congrats!

On Fri, Jun 21, 2019 at 11:55 AM Tanay Tummalapalli 
wrote:

> Congratulations!
>
> On Fri, Jun 21, 2019 at 10:35 PM Rui Wang  wrote:
>
>> Congrats!
>>
>>
>> -Rui
>>
>> On Fri, Jun 21, 2019 at 9:58 AM Robin Qiu  wrote:
>>
>>> Congrats, Mikhail!
>>>
>>> On Fri, Jun 21, 2019 at 9:12 AM Alexey Romanenko <
>>> aromanenko@gmail.com> wrote:
>>>
 Congrats, Mikhail!

 On 21 Jun 2019, at 18:01, Anton Kedin  wrote:

 Congrats!

 On Fri, Jun 21, 2019 at 3:55 AM Reza Rokni  wrote:

> Congratulations!
>
> On Fri, 21 Jun 2019, 12:37 Robert Burke,  wrote:
>
>> Congrats
>>
>> On Fri, Jun 21, 2019, 12:29 PM Thomas Weise  wrote:
>>
>>> Hi,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new
>>> committer: Mikhail Gryzykhin.
>>>
>>> Mikhail has been contributing to Beam and actively involved in the
>>> community for over a year. He developed the community build dashboard 
>>> [1]
>>> and added substantial improvements to our build infrastructure. 
>>> Mikhail's
>>> work also covers metrics, contributor documentation, development process
>>> improvements and other areas.
>>>
>>> In consideration of Mikhail's contributions, the Beam PMC trusts him
>>> with the responsibilities of a Beam committer [2].
>>>
>>> Thank you, Mikhail, for your contributions and looking forward to
>>> many more!
>>>
>>> Thomas, on behalf of the Apache Beam PMC
>>>
>>> [1] https://s.apache.org/beam-community-metrics
>>> [2]
>>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>
>>>

Jira tracker permission

[Yichi Zhang]

Hi, beam-dev,

This is Yichi Zhang from Google, I just started looking into beam projects and 
will be actively working on beam sdk, could someone grant me permission to beam 
jira issue tracker? My jira username is yichi 
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=yichi>.

Looking forward to work with everyone else.

Thanks,
Yichi

Jira issue tracker permission

[Yichi Zhang]

Hi, beam-dev,

This is Yichi Zhang from Google, I just started looking into beam projects
and will be actively working on beam sdk, could someone grant me permission
to beam jira issue tracker? My jira username is yichi
<https://issues.apache.org/jira/secure/ViewProfile.jspa?name=yichi>.

Looking forward to work with everyone else.

Thanks,
Yichi