Re: [ANNOUNCE] New committer: Steven Niemitz

[Connell O'Callaghan via dev]

+++1 Woohoo! Congratulations Steven (and to the BEAM community) on this
announcement!!!

Thank you Luke for this update


On Tue, Jul 19, 2022 at 12:34 PM Robert Burke  wrote:

> Woohoo! Welcome and congratulations Steven!
>
> On Tue, Jul 19, 2022, 12:40 PM Luke Cwik via dev 
> wrote:
>
>> Hi all,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new committer:
>> Steven Niemitz (sniemitz@)
>>
>> Steven started contributing to Beam in 2017 fixing bugs and improving
>> logging and usability. Stevens most recent focus has been on performance
>> optimizations within the Java SDK.
>>
>> Considering the time span and number of contributions, the Beam PMC
>> trusts Steven with the responsibilities of a Beam committer. [1]
>>
>> Thank you Steven! And we are looking to see more of your contributions!
>>
>> Luke, on behalf of the Apache Beam PMC
>>
>> [1] https://beam.apache.org/contribute/become-a-committer
>> /#an-apache-beam-committer
>>
>

unsubscribe

[Connell O'Callaghan]

unsubscribe

Re: [ANNOUNCE] New PMC Member: Chamikara Jayalath

[Connell O'Callaghan]

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 
> wrote:
>
>> Congratulations, Cham!
>>
>> On Thu, Jan 21, 2021 at 3:13 PM Brian Hulette 
>> 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 
 wrote:

> Woo! Congrats Cham!
>
> On Thu, Jan 21, 2021 at 3:02 PM Robert Burke 
> 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 
>>> wrote:
>>>
 Congrats Cham!

 On Thu, Jan 21, 2021 at 2:57 PM Ahmet Altay 
 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
>

Re: [ANNOUNCE] New committer: Reza Ardeshir Rokni

[Connell O'Callaghan]

Excellent- well done Reza!!!

On Thu, Sep 10, 2020 at 7:35 PM Austin Bennett 
wrote:

> Thanks and congrats, Reza!
>
> On Thu, Sep 10, 2020 at 5:48 PM Heejong Lee  wrote:
>
>> Congratulations!
>>
>> On Thu, Sep 10, 2020 at 4:42 PM Robert Bradshaw 
>> wrote:
>>
>>> Thank you and welcome, Reza!
>>>
>>> On Thu, Sep 10, 2020 at 4:00 PM Ahmet Altay  wrote:
>>>
 Congratulations Reza! And thank you for your contributions!

 On Thu, Sep 10, 2020 at 3:59 PM Chamikara Jayalath <
 chamik...@google.com> wrote:

> Congrats Reza!
>
> On Thu, Sep 10, 2020 at 10:35 AM Kenneth Knowles 
> wrote:
>
>> Hi all,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new
>> committer: Reza Ardeshir Rokni.
>>
>> Reza has been part of the Beam community since 2017! Reza has
>> spearheaded advanced Beam examples [1], blogged and presented at multiple
>> Beam Summits. Reza helps out users on the mailing lists [2] and
>> StackOverflow [3]. When Reza's work uncovers a missing feature in Beam, 
>> he
>> adds it [4]. Considering these contributions, the Beam PMC trusts Reza 
>> with
>> the responsibilities of a Beam committer [5].
>>
>> Thank you, Reza, for your contributions.
>>
>> Kenn
>>
>> [1] https://github.com/apache/beam/pull/3961
>> [2]
>> https://lists.apache.org/list.html?u...@beam.apache.org:gte=0d:reza%20rokni
>> [3] https://stackoverflow.com/tags/apache-beam/topusers
>> [4] https://github.com/apache/beam/pull/11929
>> [5]
>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>
>>
>>
>
>


>>>
>>>
>>
>>
>
> --
Your feedback welcomed for Connello!!!

Re: Greetings from Tyson

[Connell O'Callaghan]

Welcome Tyson!!!



On Thu, Apr 30, 2020 at 6:12 AM Ismaël Mejía  wrote:

> Welcome!
>
> On Thu, Apr 30, 2020 at 12:27 AM Alan Myrvold  wrote:
> >
> > Welcome, Tyson!
> >
> > On Wed, Apr 29, 2020 at 3:15 PM Rui Wang  wrote:
> >>
> >> Welcome!
> >>
> >> -Rui
> >>
> >> On Wed, Apr 29, 2020, 3:13 PM Brian Hulette 
> wrote:
> >>>
> >>> Welcome Tyson!
> >>>
> >>> On Wed, Apr 29, 2020 at 2:54 PM Ahmet Altay  wrote:
> 
>  Welcome!
> 
>  On Tue, Apr 28, 2020 at 3:06 PM Hannah Jiang 
> wrote:
> >
> > Welcome to the community!
> >
> >
> > On Tue, Apr 28, 2020 at 2:45 PM Tyson Hamilton 
> wrote:
> >>
> >> Hello Beam Community,
> >>
> >> This is just a simple 'Hello' to introduce myself. I'm a Software
> Engineer at Google and have worked with data processing languages and
> runtime systems on and off during my career. I now have the pleasure of
> dedicating more time towards working with you lovely folks on Beam and I'm
> really excited!
> >>
> >> I hope you're all doing well and staying safe in these difficult
> times.
> >>
> >> -Tyson
> >>
> >>
> >>
>

Re: [ANNOUNCE] Beam 2.19.0 Released

[Connell O'Callaghan]

Well done and thank you Boyuan (and all involved)!!!

On Tue, Feb 4, 2020 at 4:25 PM Boyuan Zhang  wrote:

> The Apache Beam team is pleased to announce the release of version 2.19.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/02/04/beam-2.19.0.html
>
> Thanks to everyone who contributed to this release, and we hope you enjoy
> using Beam 2.19.0.
> -- Boyuan Zhang, on behalf of The Apache Beam team
>

Re: [ANNOUNCE] New committer: Michał Walenia

[Connell O'Callaghan]

Thank you Pablo for sharing!!!

Well done Michal!!!

On Tue, Jan 28, 2020 at 21:07 jincheng sun  wrote:

> Congrats Michał ！
>
>
> Hannah Jiang 于2020年1月29日 周三01:43写道：
>
>> Congrats you Michal!
>>
>>
>>
>> On Tue, Jan 28, 2020 at 9:11 AM Gleb Kanterov  wrote:
>>
>>> Congratulations!
>>>
>>> On Tue, Jan 28, 2020 at 6:03 PM Łukasz Gajowy 
>>> wrote:
>>>
 Congratulations Michał! 

 wt., 28 sty 2020 o 16:33 Ryan Skraba  napisał(a):

> Congratulations!
>
> On Tue, Jan 28, 2020 at 11:26 AM Jan Lukavský  wrote:
>
>> Congrats Michał!
>> On 1/28/20 11:16 AM, Katarzyna Kucharczyk wrote:
>>
>> Congratulations Michał!  
>>
>> On Tue, Jan 28, 2020 at 9:29 AM Alexey Romanenko <
>> aromanenko@gmail.com> wrote:
>>
>>> Congrats, Michał!
>>>
>>> On 28 Jan 2020, at 09:20, Ismaël Mejía  wrote:
>>>
>>> Congratulations Michał, well deserved!
>>>
>>> On Tue, Jan 28, 2020 at 8:54 AM Kamil Wasilewski <
>>> kamil.wasilew...@polidea.com> wrote:
>>>
 Congrats, Michał!

 On Tue, Jan 28, 2020 at 3:03 AM Udi Meiri  wrote:

> Congratulations Michał!
>
> On Mon, Jan 27, 2020 at 3:49 PM Chamikara Jayalath <
> chamik...@google.com> wrote:
>
>> Congrats Michał!
>>
>> On Mon, Jan 27, 2020 at 2:59 PM Reza Rokni 
>> wrote:
>>
>>> Congratulations buddy!
>>>
>>> On Tue, 28 Jan 2020, 06:52 Valentyn Tymofieiev, <
>>> valen...@google.com> wrote:
>>>
 Congratulations, Michał!

 On Mon, Jan 27, 2020 at 2:24 PM Austin Bennett <
 whatwouldausti...@gmail.com> wrote:

> Nice -- keep up the good work!
>
> On Mon, Jan 27, 2020 at 2:02 PM Mikhail Gryzykhin <
> mig...@google.com> wrote:
> >
> > Congratulations Michal!
> >
> > --Mikhail
> >
> > On Mon, Jan 27, 2020 at 1:01 PM Kyle Weaver <
> kcwea...@google.com> wrote:
> >>
> >> Congratulations Michał! Looking forward to your future
> contributions :)
> >>
> >> Thanks,
> >> Kyle
> >>
> >> On Mon, Jan 27, 2020 at 12:47 PM Pablo Estrada <
> pabl...@google.com> wrote:
> >>>
> >>> Hi everyone,
> >>>
> >>> Please join me and the rest of the Beam PMC in welcoming a
> new committer: Michał Walenia
> >>>
> >>> Michał has contributed to Beam in many ways, including the
> performance testing infrastructure, and has even spoken at events 
> about
> Beam.
> >>>
> >>> In consideration of his contributions, the Beam PMC trusts
> him with the responsibilities of a Beam committer[1].
> >>>
> >>> Thanks for your contributions Michał!
> >>>
> >>> Pablo, on behalf of the Apache Beam PMC.
> >>>
> >>> [1]
> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>

>>> --
>
> Best,
> Jincheng
> -
> Twitter: https://twitter.com/sunjincheng121
> -
>

Re: [ANNOUNCE] New committer: Hannah Jiang

[Connell O'Callaghan]

Thank you for sharing Luke!!!

Well done and congratulations Hannah!!

On Tue, Jan 28, 2020 at 4:45 PM Heejong Lee  wrote:

> Congratulations! :)
>
> On Tue, Jan 28, 2020 at 4:43 PM Yichi Zhang  wrote:
>
>> 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

[Connell O'Callaghan]

Well done thank you Udi!!!

On Tue, Jan 28, 2020 at 11:47 AM Ankur Goenka  wrote:

> Thanks Udi!
>
> On Tue, Jan 28, 2020 at 11:30 AM Yichi Zhang  wrote:
>
>> 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: [ANNOUNCE] New committer: Daniel Oliveira

[Connell O'Callaghan]

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 
 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

[Connell O'Callaghan]

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  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  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 
>> 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.
>>
>

Re: [ANNOUNCE] New committer: Alan Myrvold

[Connell O'Callaghan]

Congratulations Alan - well done!!! Ahmet thank you for sharing this great
news!!!

On Mon, Sep 30, 2019 at 7:34 AM Łukasz Gajowy  wrote:

> Congratulations :)
>
> pon., 30 wrz 2019 o 15:41 Reza Rokni  napisał(a):
>
>> Woohoo Congratulations!
>>
>> On Mon, 30 Sep 2019 at 21:06, Thomas Weise  wrote:
>>
>>> Congratulations, Alan!
>>>
>>>
>>> On Mon, Sep 30, 2019 at 4:47 AM Ismaël Mejía  wrote:
>>>
 Congrats Alan!

 On Mon, Sep 30, 2019, 11:20 AM Tanay Tummalapalli 
 wrote:

> Congratulations, Alan!
>
>
> On Mon, Sep 30, 2019 at 1:03 PM Gleb Kanterov 
> wrote:
>
>> Congratulations!
>>
>> On Sat, Sep 28, 2019 at 12:07 AM Valentyn Tymofieiev <
>> valen...@google.com> wrote:
>>
>>> Congratulations, Alan. Well deserved.
>>>
>>> On Fri, Sep 27, 2019 at 2:09 PM Chamikara Jayalath <
>>> chamik...@google.com> wrote:
>>>
 Congrats Alan!!

 On Fri, Sep 27, 2019 at 1:49 PM Jan Lukavský 
 wrote:

> Congrats Alan!
> On 9/27/19 10:22 PM, Mark Liu wrote:
>
> Congratulations Alan!!!
>
> On Fri, Sep 27, 2019 at 12:55 PM Ning Kang 
> wrote:
>
>> Congrats Alan!
>>
>> On Fri, Sep 27, 2019 at 12:02 PM Ankur Goenka 
>> wrote:
>>
>>> Congratulations Alan!
>>>
>>> On Fri, Sep 27, 2019 at 11:17 AM Yichi Zhang 
>>> wrote:
>>>
 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 <
> hannahji...@google.com> wrote:
>
>> Congrats Alan!
>>
>> On Fri, Sep 27, 2019 at 9:57 AM Ruoyun Huang <
>> ruo...@google.com> 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 <
 pabl...@google.com> wrote:

> Yooh! : D
>
> On Fri, Sep 27, 2019 at 9:53 AM Yifan Zou <
> yifan...@google.com> wrote:
>
>> Congratulations, Alan!
>>
>> On Fri, Sep 27, 2019 at 9:18 AM Ahmet Altay <
>> al...@google.com> 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
>>>
>>>
>>
>> --
>> Cheers,
>> Gleb
>>
>
>>
>> --
>>
>> 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.
>>
>

Re: [ANNOUNCE] New committer: Valentyn Tymofieiev

[Connell O'Callaghan]

Congratulations Valentyn!!!

- Connell

On Tue, Sep 3, 2019 at 9:34 AM David Cavazos  wrote:

> Congratulations Valentyn! 
>
> On Mon, Sep 2, 2019 at 7:12 PM jincheng sun 
> wrote:
>
>> Congrats Valentyn !
>>
>> Cheers,
>> Jincheng
>>
>> Katarzyna Kucharczyk  于2019年9月2日周一 下午5:20写道：
>>
>>> Congratulations Valentyn! 
>>>
>>> On Wed, Aug 28, 2019 at 3:49 PM Frederik Bode 
>>> wrote:
>>>
 Congrats Valentyn!!


 On Wed, 28 Aug 2019 at 15:28, Tanay Tummalapalli 
 wrote:

> Congratulations Valentyn!
>
> On Wed, Aug 28, 2019 at 7:16 AM Ruoyun Huang 
> wrote:
>
>> Congratulations Valentyn!
>>
>> On Tue, Aug 27, 2019 at 6:16 PM Daniel Oliveira <
>> danolive...@google.com> wrote:
>>
>>> Congratulations Valentyn!
>>>
>>> On Tue, Aug 27, 2019, 11:31 AM Boyuan Zhang 
>>> wrote:
>>>
 Congratulations!

 On Tue, Aug 27, 2019 at 10:44 AM Udi Meiri 
 wrote:

> Congrats!
>
> On Tue, Aug 27, 2019 at 9:50 AM Yichi Zhang 
> wrote:
>
>> Congrats Valentyn!
>>
>> On Tue, Aug 27, 2019 at 7:55 AM Valentyn Tymofieiev <
>> valen...@google.com> wrote:
>>
>>> Thank you everyone!
>>>
>>> On Tue, Aug 27, 2019 at 2:57 AM Alexey Romanenko <
>>> aromanenko@gmail.com> 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 <
 hannahji...@google.com> wrote:

> Congratulations Valentyn, well deserved!
>
> On Mon, Aug 26, 2019 at 2:34 PM Chamikara Jayalath <
> chamik...@google.com> wrote:
>
>> Congrats Valentyn!
>>
>> On Mon, Aug 26, 2019 at 2:32 PM Pablo Estrada <
>> pabl...@google.com> wrote:
>>
>>> Thanks Valentyn!
>>>
>>> On Mon, Aug 26, 2019 at 2:29 PM Robin Qiu <
>>> robi...@google.com> wrote:
>>>
 Thank you Valentyn! Congratulations!

 On Mon, Aug 26, 2019 at 2:28 PM Robert Bradshaw <
 rober...@google.com> 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
>


>>
>> --
>> 
>> Ruoyun  Huang
>>
>>

Re: [ANNOUNCE] Beam 2.15.0 Released!

[Connell O'Callaghan]

+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

[Connell O'Callaghan]

Well done Rui!!!

On Tue, Aug 6, 2019 at 15:41 Chamikara Jayalath 
wrote:

> Congrats Rui.
>
> On Tue, Aug 6, 2019 at 2:00 PM Melissa Pashniak 
> wrote:
>
>> Congrats Rui!
>>
>> On Tue, Aug 6, 2019 at 1:37 PM Yichi Zhang  wrote:
>>
>>> Congrats Rui!
>>>
>>> On Tue, Aug 6, 2019 at 1:29 PM Aizhamal Nurmamat kyzy <
>>> aizha...@google.com> 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: Jan Lukavský

[Connell O'Callaghan]

Well done Jan!!!

On Tue, Aug 6, 2019 at 15:44 Chamikara Jayalath 
wrote:

> Congrats Jan!
>
> On Thu, Aug 1, 2019 at 11:10 AM Thomas Weise  wrote:
>
>> Congrats!
>>
>>
>> On Thu, Aug 1, 2019 at 8:44 AM jincheng sun 
>> wrote:
>>
>>> Congratulations Jan!
>>> Best, Jincheng
>>>
>>> Gleb Kanterov  于2019年8月1日周四 下午5:09写道：
>>>
 Congratulations!

 On Thu, Aug 1, 2019 at 3:11 PM Reza Rokni  wrote:

> Congratulations , awesome stuff !
>
> On Thu, 1 Aug 2019, 12:11 Maximilian Michels,  wrote:
>
>> Congrats, Jan! Good to see you become a committer :)
>>
>> On 01.08.19 12:37, Łukasz Gajowy wrote:
>> > Congratulations!
>> >
>> > czw., 1 sie 2019 o 11:16 Robert Bradshaw > > > napisał(a):
>> >
>> > Congratulations!
>> >
>> > On Thu, Aug 1, 2019 at 9:59 AM Jan Lukavský > > > wrote:
>> >
>> > Thanks everyone!
>> >
>> > Looking forward to working with this great community! :-)
>> >
>> > Cheers,
>> >
>> >  Jan
>> >
>> > On 8/1/19 12:18 AM, Rui Wang wrote:
>> > > Congratulations!
>> > >
>> > >
>> > > -Rui
>> > >
>> > > On Wed, Jul 31, 2019 at 10:51 AM Robin Qiu <
>> robi...@google.com
>> > > > wrote:
>> > >
>> > > Congrats!
>> > >
>> > > On Wed, Jul 31, 2019 at 10:31 AM Aizhamal Nurmamat
>> kyzy
>> > > mailto:aizha...@apache.org>>
>> wrote:
>> > >
>> > > Congratulations, Jan! Thank you for your
>> contributions!
>> > >
>> > > On Wed, Jul 31, 2019 at 10:04 AM Tanay
>> Tummalapalli
>> > > mailto:ttanay...@gmail.com>>
>> wrote:
>> > >
>> > > Congratulations!
>> > >
>> > > On Wed, Jul 31, 2019 at 10:05 PM Ahmet Altay
>> > > mailto:al...@google.com>>
>> wrote:
>> > >
>> > > Congratulations Jan! Thank you for your
>> > > contributions!
>> > >
>> > > On Wed, Jul 31, 2019 at 2:30 AM Ankur
>> Goenka
>> > > > goe...@google.com>>
>> > > wrote:
>> > >
>> > > Congratulations Jan!
>> > >
>> > > On Wed, Jul 31, 2019, 1:23 AM David
>> > > Morávek > > > > wrote:
>> > >
>> > > Congratulations Jan, well
>> deserved! ;)
>> > >
>> > > D.
>> > >
>> > > On Wed, Jul 31, 2019 at 10:17 AM
>> Ryan
>> > > Skraba > > > > wrote:
>> > >
>> > > Congratulations Jan!
>> > >
>> > > On Wed, Jul 31, 2019 at 10:10
>> AM
>> > > Ismaël Mejía <
>> ieme...@gmail.com
>> > > >
>> wrote:
>> > > >
>> > > > Hi,
>> > > >
>> > > > Please join me and the rest
>> of
>> > > the Beam PMC in welcoming a
>> new
>> > > > committer: Jan Lukavský.
>> > > >
>> > > > Jan has been contributing to
>> > > Beam for a while, he was part
>> of
>> > > the team
>> > > > that contributed the
>> Euphoria
>> > > DSL extension, and he has done
>> > > > interesting improvements
>> for the
>> > > Spark and Direct runner. He
>> has also
>> > > > been active in the community
>> > > discussions around the Beam
>> model and
>> > > > other subjects.
>> > > >
>> > > > In consideration of Jan's
>> > > contributions, the Beam PMC
>> trusts
>> > > him with
>> > > 

Re: [ANNOUNCE] New committer: Kyle Weaver

[Connell O'Callaghan]

Well done congratulations Kyle!!!

On Tue, Aug 6, 2019 at 21:58 Thomas Weise  wrote:

> Congrats!
>
> On Tue, Aug 6, 2019, 7:24 PM Reza Rokni  wrote:
>
>> Congratz!
>>
>> On Wed, 7 Aug 2019 at 06:40, Chamikara Jayalath 
>> wrote:
>>
>>> Congrats!!
>>>
>>> On Tue, Aug 6, 2019 at 3:33 PM Udi Meiri  wrote:
>>>
 Congrats Kyle!

 On Tue, Aug 6, 2019 at 2:00 PM Melissa Pashniak 
 wrote:

> Congratulations Kyle!
>
> On Tue, Aug 6, 2019 at 1:36 PM Yichi Zhang  wrote:
>
>> Congrats Kyle!
>>
>> On Tue, Aug 6, 2019 at 1:29 PM Aizhamal Nurmamat kyzy <
>> aizha...@google.com> 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 <
 david.mora...@gmail.com> 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
>>>
>>
>>
>> --
>>
>> 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.
>>
>

Re: [ANNOUNCE] New committer: Robert Burke

[Connell O'Callaghan]

Excellent - congratulations Rebo

On Tue, Jul 16, 2019 at 4:38 PM Tanay Tummalapalli 
wrote:

> Congratulations!
>
> On Wed, Jul 17, 2019 at 3:27 AM Aizhamal Nurmamat kyzy <
> aizha...@google.com> wrote:
>
>> Congratulations, Rebo
>>
>> On Tue, Jul 16, 2019 at 1:34 PM Chamikara Jayalath 
>> wrote:
>>
>>> Congrats!!
>>>
>>> On Tue, Jul 16, 2019 at 1:31 PM Robin Qiu  wrote:
>>>
 Congrats, Robert!!

 On Tue, Jul 16, 2019 at 1:22 PM Alan Myrvold 
 wrote:

> Congrats, Robert!
>
> On Tue, Jul 16, 2019 at 11:46 AM Ismaël Mejía 
> wrote:
>
>> Congrats Robert!
>>
>>
>> On Tue, Jul 16, 2019 at 8:19 PM Yichi Zhang 
>> wrote:
>> >
>> > 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 <
>> mig...@google.com> 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: [ANNOUNCE] New committer: Mikhail Gryzykhin

[Connell O'Callaghan]

Thomas thank you for sharing this

Congratulations on this Mikhail!!!

On Mon, Jun 24, 2019 at 3:19 PM Kai Jiang  wrote:

> Congrats!
>
> On Mon, Jun 24, 2019 at 1:46 PM Chamikara Jayalath 
> wrote:
>
>> Congrats!!
>>
>> On Mon, Jun 24, 2019 at 11:12 AM Mikhail Gryzykhin 
>> wrote:
>>
>>> Thank you everyone.
>>>
>>> On Mon, Jun 24, 2019 at 2:28 AM Aizhamal Nurmamat kyzy <
>>> aizha...@google.com> wrote:
>>>
 Congrats Misha!

 On Mon, Jun 24, 2019 at 11:23 Łukasz Gajowy  wrote:

> Congratulations Mikhail!
>
> pt., 21 cze 2019 o 22:09 Ruoyun Huang  napisał(a):
>
>> Congratulations! Mikhail!
>>
>>
>> On Fri, Jun 21, 2019 at 1:00 PM Yichi Zhang 
>> wrote:
>>
>>> Congrats!
>>>
>>> On Fri, Jun 21, 2019 at 11:55 AM Tanay Tummalapalli <
>>> ttanay...@gmail.com> 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
>> 
>>
>>
>>>
>>
>> --
>> 
>> Ruoyun  Huang
>>
>>

Re: [ANNOUNCE] New PMC Member: Pablo Estrada

[Connell O'Callaghan]

Awesome well done Pablo!!!

Kenn thank you for sharing this great news with us!!!

On Tue, May 14, 2019 at 11:01 PM Ahmet Altay  wrote:

> Congratulations!
>
> On Tue, May 14, 2019 at 9:11 PM Robert Burke  wrote:
>
>> Woohoo! Well deserved.
>>
>> On Tue, May 14, 2019, 8:34 PM Reuven Lax  wrote:
>>
>>> Congratulations!
>>>
>>> *From: *Mikhail Gryzykhin 
>>> *Date: *Tue, May 14, 2019 at 8:32 PM
>>> *To: * 
>>>
>>> Congratulations Pablo!

 On Tue, May 14, 2019, 20:25 Kenneth Knowles  wrote:

> Hi all,
>
> Please join me and the rest of the Beam PMC in welcoming Pablo Estrada
> to join the PMC.
>
> Pablo first picked up BEAM-722 in October of 2016 and has been a
> steady part of the Beam community since then. In addition to technical 
> work
> on Beam Python & Java & runners, I would highlight how Pablo grows Beam's
> community by helping users, working on GSoC, giving talks at Beam Summits
> and other OSS conferences including Flink Forward, and holding training
> workshops. I cannot do justice to Pablo's contributions in a single
> paragraph.
>
> Thanks Pablo, for being a part of Beam.
>
> Kenn
>

Re: Beam at Google Summer of Code 2019

[Connell O'Callaghan]

Well done Tanay - good luck with this project!!!

+1 Pablo - thank you for this mentorship!!!

On Mon, May 6, 2019 at 1:11 PM Chamikara Jayalath 
wrote:

> Congrats Tanay and thanks Pablo for mentoring :)
>
> On Mon, May 6, 2019 at 11:53 AM Aizhamal Nurmamat kyzy <
> aizha...@google.com> wrote:
>
>> Congratulations Tanay!
>>
>> *From: *Pablo Estrada 
>> *Date: *Mon, May 6, 2019 at 11:34 AM
>> *To: *dev, 
>>
>> Hello all,
>>> it is my pleasure to share with everyone that Tanay Tummalapalli has
>>> been accepted as a GSoC student with Beam, to implement support for File
>>> Loads into BigQuery for streaming pipelines[1].
>>>
>>> Tanay wrote a very strong proposal, and showed understanding of the
>>> tricky streaming considerations that will play out in this project.
>>>
>>> I speak on behalf of everyone welcoming you Tanay, and we'll be happy to
>>> see your contributions to Beam. : )
>>> Best
>>> -P.
>>>
>>> [1]
>>> https://summerofcode.withgoogle.com/projects/?sp-search=Tanay#4999837794172928
>>>
>>

Re: [ANNOUNCE] New committer announcement: Udi Meiri

[Connell O'Callaghan]

Well done Udi!!! Congratulations and thank you for your contributions!!!

Kenn thank you for sharing!!!

On Fri, May 3, 2019 at 2:49 PM Yifan Zou  wrote:

> Thanks Udi and congratulations!
>
> On Fri, May 3, 2019 at 2:47 PM Robin Qiu  wrote:
>
>> Congratulations Udi!!!
>>
>> *From: *Ruoyun Huang 
>> *Date: *Fri, May 3, 2019 at 2:39 PM
>> *To: * 
>>
>> Congratulations Udi!
>>>
>>> On Fri, May 3, 2019 at 2:30 PM Ahmet Altay  wrote:
>>>
 Congratulations, Udi!

 *From: *Kyle Weaver 
 *Date: *Fri, May 3, 2019 at 2:11 PM
 *To: * 

 Congratulations Udi! I look forward to sending you all my reviews for
> the next month (just kidding :)
>
> Kyle Weaver | Software Engineer | github.com/ibzib |
> kcwea...@google.com | +1650203
>
> On Fri, May 3, 2019 at 1:52 PM Charles Chen  wrote:
> >
> > Thank you Udi!
> >
> > On Fri, May 3, 2019, 1:51 PM Aizhamal Nurmamat kyzy <
> aizha...@google.com> wrote:
> >>
> >> Congratulations, Udi! Thank you for all your contributions!!!
> >>
> >> From: Pablo Estrada 
> >> Date: Fri, May 3, 2019 at 1:45 PM
> >> To: dev
> >>
> >>> Thanks Udi and congrats!
> >>>
> >>> On Fri, May 3, 2019 at 1:44 PM Kenneth Knowles 
> wrote:
> 
>  Hi all,
> 
>  Please join me and the rest of the Beam PMC in welcoming a new
> committer: Udi Meiri.
> 
>  Udi has been contributing to Beam since late 2017, starting with
> HDFS support in the Python SDK and continuing with a ton of Python work. I
> also will highlight his work on community-building infrastructure,
> including documentation, experiments with ways to find reviewers for pull
> requests, gradle build work, analyzing and reducing build times.
> 
>  In consideration of Udi's contributions, the Beam PMC trusts Udi
> with the responsibilities of a Beam committer [1].
> 
>  Thank you, Udi, for your contributions.
> 
>  Kenn
> 
>  [1]
> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>

>>>
>>> --
>>> 
>>> Ruoyun  Huang
>>>
>>>

Re: Congrats to Beam's first 6 Google Open Source Peer Bonus recipients!

[Connell O'Callaghan]

Well done - congratulations to you all!!! Rose thank you for sharing this
news!!!

On Wed, May 1, 2019 at 19:45 Rose Nguyen  wrote:

> Matthias Baetens, Lukazs Gajowy, Suneel Marthi, Maximilian Michels, Alex
> Van Boxel, and Thomas Weise:
>
> Thank you for your exceptional contributions to Apache Beam. I'm looking
> forward to seeing this project grow and for more folks to contribute and be
> recognized! Everyone can read more about this award on the Google Open
> Source blog:
> https://opensource.googleblog.com/2019/04/google-open-source-peer-bonus-winners.html
>
> Cheers,
> --
> Rose Thị Nguyễn
>

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

[Connell O'Callaghan]

Thank you Andrew!!!

On Mon, Apr 29, 2019 at 9:21 AM Andrew Pilloud  wrote:

> Yes, they were moved and are now at
> https://dist.apache.org/repos/dist/release/beam/2.12.0/
>
> On Fri, Apr 26, 2019 at 2:02 AM Robert Bradshaw 
> wrote:
> >
> > Thanks for all the hard work!
> >
> > https://dist.apache.org/repos/dist/dev/beam/2.12.0/ seems empty; were
> > the artifacts already moved?
> >
> > On Fri, Apr 26, 2019 at 10:31 AM Etienne Chauchot 
> wrote:
> > >
> > > Hi,
> > > Thanks for all your work and patience Andrew !
> > >
> > > PS: as a side note, there were 5 binding votes (I voted +1)
> > >
> > > Etienne
> > >
> > > Le jeudi 25 avril 2019 à 11:16 -0700, Andrew Pilloud a écrit :
> > >
> > > I reran the Nexmark tests, each runner passed. I compared the numbers
> > >
> > > on the direct runner to the dashboard and they are where they should
> > >
> > > be.
> > >
> > >
> > > With that, I'm happy to announce that we have unanimously approved
> this release.
> > >
> > >
> > > There are 8 approving votes, 4 of which are binding:
> > >
> > > * Jean-Baptiste Onofré
> > >
> > > * Lukasz Cwik
> > >
> > > * Maximilian Michels
> > >
> > > * Ahmet Altay
> > >
> > >
> > > There are no disapproving votes.
> > >
> > >
> > > Thanks everyone!
> > >
> > >
>

Re: Hello from Hannah Jiang

[Connell O'Callaghan]

Welcome Hannah!!!

On Thu, Apr 25, 2019, 5:42 PM Reza Rokni  wrote:

> Welcome!
>
> On Fri, 26 Apr 2019 at 04:36, Hannah Jiang  wrote:
>
>> Thanks Cyrus!
>>
>> On Thu, Apr 25, 2019 at 1:34 PM Cyrus Maden  wrote:
>>
>>> Welcome!!
>>>
>>> On Thu, Apr 25, 2019 at 4:30 PM Hannah Jiang 
>>> wrote:
>>>
 Thank you Robin!

 On Thu, Apr 25, 2019 at 1:27 PM Robin Qiu  wrote:

> Welcome Hannah!
>
> On Thu, Apr 25, 2019 at 1:26 PM Hannah Jiang 
> wrote:
>
>> Thanks Kenneth!
>>
>> On Thu, Apr 25, 2019 at 1:24 PM Kenneth Knowles 
>> wrote:
>>
>>> Welcome!
>>>
>>> On Thu, Apr 25, 2019 at 12:38 PM Matthias Baetens <
>>> baetensmatth...@gmail.com> wrote:
>>>
 Welcome to the community!

 On Thu, Apr 25, 2019, 18:55 Griselda Cuevas 
 wrote:

> Welcome Hannah! - Very excited to see you in the Beam community :)
>
> On Tue, 23 Apr 2019 at 12:59, Hannah Jiang 
> wrote:
>
>> Hi everyone
>>
>> I joined Google recently and would work on Python portability
>> part. I am happy to be part of the community. Looking forward to 
>> working
>> with all of you together.
>>
>> I have a minor request, can admin please give me access to JIRA?
>>
>> Thanks,
>> Hannah
>>
>>
>>
>
> --
>
> 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.
>

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

[Connell O'Callaghan]

+1 thank you Andrew!!!

On Thu, Apr 25, 2019 at 11:44 AM Tim Robertson 
wrote:

> Thank you for running the release Andrew
>
> On Thu, Apr 25, 2019 at 8:24 PM Andrew Pilloud 
> wrote:
>
>> I reran the Nexmark tests, each runner passed. I compared the numbers
>> on the direct runner to the dashboard and they are where they should
>> be.
>>
>> With that, I'm happy to announce that we have unanimously approved this
>> release.
>>
>> There are 8 approving votes, 4 of which are binding:
>> * Jean-Baptiste Onofré
>> * Lukasz Cwik
>> * Maximilian Michels
>> * Ahmet Altay
>>
>> There are no disapproving votes.
>>
>> Thanks everyone!
>>
>

Re: [ANNOUNCE] New committer announcement: Yifan Zou

[Connell O'Callaghan]

Well done Yifan!!!

Thank you for sharing Kenn!!!

On Mon, Apr 22, 2019 at 9:00 AM Ahmet Altay  wrote:

> Congratulations, Yifan!
>
> On Mon, Apr 22, 2019 at 8:46 AM Tim Robertson 
> wrote:
>
>> Congratulations Yifan!
>>
>> On Mon, Apr 22, 2019 at 5:39 PM Cyrus Maden  wrote:
>>
>>> Congratulations Yifan!!
>>>
>>> On Mon, Apr 22, 2019 at 11:26 AM Kenneth Knowles 
>>> wrote:
>>>
 Hi all,

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

 Yifan has been contributing to Beam since early 2018. He has proposed
 70+ pull requests, adding dependency checking and improving test
 infrastructure. But something the numbers cannot show adequately is the
 huge effort Yifan has put into working with infra and keeping our Jenkins
 executors healthy.

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

 Thank you, Yifan, for your contributions.

 Kenn

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

>>>

Re: New contributor to Beam

[Connell O'Callaghan]

Welcome Cyrus!!!

On Wed, Apr 17, 2019 at 10:11 AM Mikhail Gryzykhin 
wrote:

> Welcome!
>
> --Mikhail
>
> On Wed, Apr 17, 2019 at 9:58 AM Melissa Pashniak 
> wrote:
>
>>
>> Welcome Cyrus!
>>
>>
>> On Wed, Apr 17, 2019 at 7:31 AM Jean-Baptiste Onofré 
>> wrote:
>>
>>> Welcome !
>>>
>>> Regards
>>> JB
>>>
>>> On 17/04/2019 16:05, Cyrus Maden wrote:
>>> > Hi all!
>>> >
>>> > My name's Cyrus and I'd like to start contributing to Beam. I'm a
>>> > technical writer so I'm particularly looking forward to contributing to
>>> > the Beam docs. Could someone add me as a contributor on JIRA so I can
>>> > create and assign tickets?
>>> >
>>> > My JIRA name is: *cyrusmaden*
>>> > *
>>> > *
>>> > Excited to be a part of this community and to work with ya'll!
>>> >
>>> > Best,
>>> > Cyrus
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>

Re: [ANNOUNCE] New committer announcement: Boyuan Zhang

[Connell O'Callaghan]

Well done and congratulations Boyuan!!!

On Wed, Apr 10, 2019, 5:04 PM Lukasz Cwik  wrote:

> Congratulations and well deserved.
>
> On Wed, Apr 10, 2019 at 9:00 AM Kenneth Knowles  wrote:
>
>> Hi all,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new committer:
>> Boyuan Zhang.
>>
>> Boyuan has been contributing to Beam since early 2018. She has proposed
>> 100+ pull requests across a wide range of topics: bug fixes, to integration
>> tests, build improvements, metrics features, release automation. Two big
>> picture things to highlight are building/releasing Beam Python wheels and
>> managing the donation of the Beam Dataflow Java Worker, including help with
>> I.P. clearance.
>>
>> In consideration of Boyuan's contributions, the Beam PMC trusts Boyuan
>> with the responsibilities of a Beam committer [1].
>>
>> Thank you, Boyuan, for your contributions.
>>
>> Kenn
>>
>> [1] https://beam.apache.org/contribute/become-a-committer/#an-apache-beam
>> -committer
>>
>

Re: Updates on Beam Jenkins

[Connell O'Callaghan]

Yifan thank you for this update and progressing this replacement!!!

On Tue, Apr 9, 2019, 11:14 PM Yifan Zou  wrote:

> Thanks, Pablo. The new workers use custom image in the boot disk and it's
> easy to reboot without re-imaging. Means we will no longer need assistance
> from Infra to reconnect an offline node. Dockerizing the environment would
> be helpful to make changes on the environment, such as installing/updating
> a beam-required package.
>
>
> On Tue, Apr 9, 2019 at 2:39 PM Pablo Estrada  wrote:
>
>> Thanks for the updates Yifan. I am sure this process has been difficult,
>> and I appreciate the good communication, and that this didn't really affect
>> the workflow of anyone to validate the new setup for nodes.
>>
>> I imagine that once we move to dockerizing the testing environment, it
>> will be much simpler to restart machines that are having trouble?
>> Thanks again!
>> -P.
>>
>> On Tue, Apr 9, 2019 at 2:23 PM Yifan Zou  wrote:
>>
>>> Hello,
>>>
>>> I have some good news about our Jenkins nodes. We're now having 7 new
>>> nodes  online named as
>>> "apache-beam-jenkins-[1, 2, 4, 7, 8, 9, 12]", which substitute the old
>>> broken agents "beam[1, 2, 4, 7, 8, 9, 12]". This helps to reduce the job
>>> waiting queue that let your tests getting executed quickly. They're
>>> starting up and accepting jobs. There is no action needed on your end.
>>>
>>> I'll keep the remaining old agents running for one more week just in
>>> case it won't fully block the development works if any unexpected issues on
>>> the new agents. Once the new agents are stable and verified, I'll move
>>> forward to connect the rest agents and remove old set. The playbook is also
>>> on the way.
>>>
>>> For more background and information of the Jenkins updates, please see:
>>> One pager:
>>> https://docs.google.com/document/d/1c38IPrF94PZC-ItGZgmAgAKrgmC1MGA6N6nkK0cL6L4/edit?ts=5ca54b3e#
>>> Environment verification sheet:
>>> https://docs.google.com/spreadsheets/d/1MDL6vy_0iaFSZeWQ-4JWKlRiZ5WFdDVjJh6Xvczgld0/edit#gid=0
>>> Previous Thread on dev@:
>>> https://lists.apache.org/thread.html/7b9863b241b37484f321d8812e2ad10d8f054ec720aec4b98efe0446@%3Cdev.beam.apache.org%3E
>>>
>>> Thanks.
>>>
>>> Regards.
>>> Yifan Zou
>>>
>>>
>>>

Re: New contributor

[Connell O'Callaghan]

Welcome Niklas - given your background it will be very interesting to see
your contributions.

On Wed, Mar 27, 2019 at 10:29 AM Mark Liu  wrote:

> Welcome!
>
> Mark
>
> On Wed, Mar 27, 2019 at 10:09 AM Lukasz Cwik  wrote:
>
>> Welcome. The getting started[1] and contribution guides[2] are most
>> useful. I have also added you as a contributor to the JIRA project.
>>
>> 1: https://beam.apache.org/get-started/beam-overview/
>> 2: https://beam.apache.org/contribute/
>>
>> On Wed, Mar 27, 2019 at 9:38 AM Niklas Hansson <
>> niklas.sven.hans...@gmail.com> wrote:
>>
>>> Hi!
>>>
>>> I work as a data scientist within banking but will switch over to
>>> manufacturing the next month. I would like to contribute to Beam and
>>> especially the Python SDK. Could you add me as a contributor?
>>>
>>> I am new to open source contribution so feel free to give me any advice
>>> or point me in the right direction. Plan to start off with some of the
>>> starter tasks from the Jira board.
>>>
>>> Best regards
>>> Niklas
>>>
>>

Re: New contributor

[Connell O'Callaghan]

Welcome Guobao!!!

On Tue, Mar 26, 2019 at 11:09 AM Melissa Pashniak 
wrote:

> Welcome!
>
>
> On Tue, Mar 26, 2019 at 10:17 AM Kenneth Knowles  wrote:
>
>> Welcome! Cool project. A lot of code, and thorough experiments.
>>
>> Kenn
>>
>> On Tue, Mar 26, 2019 at 9:15 AM Chamikara Jayalath 
>> wrote:
>>
>>> Welcome!
>>>
>>> On Tue, Mar 26, 2019 at 8:56 AM Ahmet Altay  wrote:
>>>
 Welcome Guobao!

 On Tue, Mar 26, 2019 at 7:13 AM Ismaël Mejía  wrote:

> Welcome Guobao!
>
> Nice that you are joining us. Looking forward for your contributions !
> Take the time to read the contribution guide
> https://beam.apache.org/contribute/ and don't hesitate to ask any
> question you may have.
>
> On Tue, Mar 26, 2019 at 2:14 PM Alexey Romanenko
>  wrote:
> >
> > Welcome, Guobao! Great to have you on board!
> >
> > Alexey
> >
> > On 26 Mar 2019, at 11:49, Guobao Li  wrote:
> >
> > Hi all,
> >
> > I am Guobao Li from Talend. I am new to Apache Beam. Currently I am
> working on the implementation of CouchbaseIO and hope to contribute in 
> more
> areas in the future.
> >
> > I have some Open Source experience. I contributed on extension of a
> DSL to introduce the architecture of Parameter Server to Apache SystemML
> [1] as part of GSoC 2018. I earned comittership due to my work. So I’m 
> very
> glad to be here and continue contributing to Open Source now on Apache 
> Beam.
> >
> > Regards,
> > Guobao Li
> >
> > [1]
> https://summerofcode.withgoogle.com/archive/2018/projects/5148916517437440/
> >
> >
>

Re: [ANNOUNCE] New committer announcement: Mark Liu

[Connell O'Callaghan]

Well done congratulations Mark!!!

On Sun, Mar 24, 2019 at 10:17 PM Robert Burke  wrote:

> Congratulations Mark! 
>
> On Sun, Mar 24, 2019, 10:08 PM Valentyn Tymofieiev 
> wrote:
>
>> Congratulations, Mark!
>>
>> Thanks for your contributions, in particular for your efforts to
>> parallelize test execution for Python SDK and increase the speed of Python
>> precommit checks.
>>
>> On Sun, Mar 24, 2019 at 9:40 PM Kenneth Knowles  wrote:
>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new committer:
>>> Mark Liu.
>>>
>>> Mark has been contributing to Beam since late 2016! He has proposed 100+
>>> pull requests. Mark was instrumental in expanding test and infrastructure
>>> coverage, especially for Python. In consideration of Mark's
>>> contributions, the Beam PMC trusts Mark with the responsibilities of a Beam
>>>  committer [1].
>>>
>>> Thank you, Mark, for your contributions.
>>>
>>> Kenn
>>>
>>> [1] https://beam.apache.org/contribute/become-a-committer/#an-apache-
>>> beam-committer
>>>
>>

Re: hi from DevRel land

[Connell O'Callaghan]

Welcome on board Reza!!!

On Wed, Mar 13, 2019 at 8:41 PM Joana Filipa Bernardo Carrasqueira <
joanafil...@google.com> wrote:

> Welcome Reza!
>
> On Wed, Mar 13, 2019 at 3:12 PM David Cavazos  wrote:
>
>> Welcome Reza!
>>
>> On Wed, Mar 13, 2019 at 9:48 AM Mark Liu  wrote:
>>
>>> Welcome Reza!
>>>
>>> On Wed, Mar 13, 2019 at 8:09 AM Etienne Chauchot 
>>> wrote:
>>>
 Welcome onboard Reza

 Etienne

 Le mardi 12 mars 2019 à 09:10 -0700, Rose Nguyen a écrit :

 Welcome, Reza! Really excited to have you!

 On Tue, Mar 12, 2019 at 9:00 AM Reza Ardeshir Rokni 
 wrote:

 Thanx folks!

 Oppsy on the link, here it is again:

 https://stackoverflow.com/questions/54422510/how-to-solve-duplicate-values-exception-when-i-create-pcollectionviewmapstring/54623618#54623618

 On Tue, 12 Mar 2019 at 23:32, Teja MVSR  wrote:

 Hi Reza,

 I am also interested to contribute towards documentation. Please let me
 know if I can be of any help.

 Thanks and Regards,
 Teja.

 On Tue, Mar 12, 2019, 11:30 AM Kenneth Knowles  wrote:

 This is great news.

 For the benefit of the list, I want to say how nice it has been when I
 have had a chance to work with you. I've learned a great deal real and
 complex use cases through those opportunities. I'm really excited that
 you'll be helping out Beam in this new role.

 Kenn

 On Tue, Mar 12, 2019 at 7:21 AM Valentyn Tymofieiev <
 valen...@google.com> wrote:

 Hi Reza!

 Welcome to Beam. Very nice to have you onboard. Btw, the link seems
 broken.

 Thanks,
 Valentyn

 On Tue, Mar 12, 2019 at 6:04 AM Reza Ardeshir Rokni 
 wrote:

 Hi Folks,

 Just wanted to say hi to the good folks in the Beam community in my new
 capacity as a Developer advocate for Beam/Dataflow @ Google. :-)

 At the moment I am working on a couple of blogs around the Timer and
 State API as well as some work on general patterns that I hope to
 contribute as documentation to the Beam site. An example of the patterns
 can be seen here:  LINK

 Hope to be adding many more in 2019 and really looking forward to being
 able to contribute to Beam in anyway that I can!

 Cheers
 Reza




>
> --
>
> *Joana Carrasqueira*
>
> Cloud Developer Relations Events Manager
>
> 415-602-2507 Mobile
>
> 1160 N Mathilda Ave, Sunnyvale, CA 94089
>
>
>

Re: New contributor to Beam

[Connell O'Callaghan]

Hi Aizhamal welcome!!

On Mon, Mar 11, 2019 at 11:08 AM Rose Nguyen  wrote:

> Welcome, Aizhamal!
>
> On Mon, Mar 11, 2019 at 10:55 AM Ahmet Altay  wrote:
>
>> Welcome!
>>
>> On Fri, Mar 8, 2019 at 3:25 PM Ismaël Mejía  wrote:
>>
>>> Done, welcome !
>>>
>>> On Fri, Mar 8, 2019 at 11:03 PM Aizhamal Nurmamat kyzy
>>>  wrote:
>>> >
>>> > Hello everyone!
>>> >
>>> > My name is Aizhamal and I would like to start contributing to Beam.
>>> Can anyone add me as a contributor for Beam's Jira issue tracker? I would
>>> like to create and assign tickets.
>>> >
>>> > My jira username is aizhamal.
>>> >
>>> > Thanks and excited to be part of this community!
>>> > Aizhamal
>>>
>>
>
> --
> Rose Thị Nguyễn
>

Re: [ANNOUNCE] New committer announcement: Raghu Angadi

[Connell O'Callaghan]

Congratulation Raghu!!! Thank you for sharing Kenn!!!

On Thu, Mar 7, 2019 at 9:55 AM Ismaël Mejía  wrote:

> Congrats !
>
> Le jeu. 7 mars 2019 à 17:09, Aizhamal Nurmamat kyzy 
> a écrit :
>
>> Congratulations, Raghu!!!
>> On Thu, Mar 7, 2019 at 08:07 Kenneth Knowles  wrote:
>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new committer:
>>> Raghu Angadi
>>>
>>> Raghu has been contributing to Beam since early 2016! He has
>>> continuously improved KafkaIO and supported on the user@ list but his
>>> community contributions are even more extensive, including reviews, dev@
>>> list discussions, improvements and ideas across SqsIO, FileIO, PubsubIO,
>>> and the Dataflow and Samza runners. In consideration of Raghu's
>>> contributions, the Beam PMC trusts Raghu with the responsibilities of a
>>> Beam committer [1].
>>>
>>> Thank you, Raghu, for your contributions.
>>>
>>> Kenn
>>>
>>> [1] https://beam.apache.org/contribute/become-a-committer/#an-apache-
>>> beam-committer
>>>
>>

Re: [VOTE] Release 2.11.0, release candidate #2

[Connell O'Callaghan]

Excellent thank you Ahmet and all involved!!!

On Fri, Mar 1, 2019, 7:23 AM Ahmet Altay  wrote:

> Thank you everyone for voting.
>
> The vote has passed with 5 supportive +1 votes, 4 of which are binding PMC
> votes:
>
> * Maximilian Michels
> * Reuven Lax
> * Kenneth Knowles
> * Ahmet Altay
>
> I will proceed with release finalization steps.
>
> Ahmet
>
> On Fri, Mar 1, 2019 at 6:59 AM Ahmet Altay  wrote:
>
>> +1 (binding)
>>
>> On Tue, Feb 26, 2019 at 9:18 PM Kenneth Knowles  wrote:
>>
>>> +1 (binding)
>>>
>>> Ran run_rc_validation.sh and said "yes" to everything up to one mobile
>>> gaming example. I did not get to the Python tests towards the end of the
>>> script (it is the same as last RC anyhow? I did not verify this)
>>>
>>> On Tue, Feb 26, 2019 at 2:16 PM Charles Chen  wrote:
>>>
 Thank you, +1.  I tested Python 3 support in batch and streaming mode
 (using wordcount and streaming wordcount) on both DirectRunner and
 DataflowRunner.

 On Tue, Feb 26, 2019 at 7:54 AM Konstantinos Katsiapis <
 katsia...@google.com> wrote:

> +1.
> (Same rational as my earlier post for RC1).
>
> On Tue, Feb 26, 2019 at 2:19 AM Maximilian Michels 
> wrote:
>
>> +1 (binding)
>>
>> * Verified checksums
>> * Ran quickstart WordCount tests local/cluster with the Flink Runner
>>
>> -Max
>>
>> On 26.02.19 10:40, Ahmet Altay wrote:
>> > Hi everyone,
>> >
>> > Please review and vote on the release candidate #2 for the version
>> > 2.11.0, as follows:
>> >
>> > [ ] +1, Approve the release
>> > [ ] -1, Do not approve the release (please provide specific
>> comments)
>> >
>> > 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 64B84A5AD91F9C20F5E9D9A7D62E71416096FA00 [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "v2.11.0-RC2" [5],
>> > * website pull request listing the release [6] and publishing the
>> API
>> > reference manual [7].
>> > * Python artifacts are deployed along with the source release to
>> the
>> > dist.apache.org  [2].
>> > * Validation sheet with a tab for 2.11.0 release to help with
>> validation
>> > [8].
>> >
>> > The vote will be open for at least 72 hours. It is adopted by
>> majority
>> > approval, with at least 3 PMC affirmative votes.
>> >
>> > Thanks,
>> > Ahmet
>> >
>> > [1]
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12344775
>> > [2] https://dist.apache.org/repos/dist/dev/beam/2.11.0/
>> > [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> > [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1064/
>> > [5] https://github.com/apache/beam/tree/v2.11.0-RC2
>> > [6] https://github.com/apache/beam/pull/7924
>> > [7] https://github.com/apache/beam-site/pull/587
>> > [8]
>> >
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=542393513
>> >
>>
>
>
> --
> Gus Katsiapis | Software Engineer | katsia...@google.com |
>  650-918-7487
>

Re: [ANNOUNCE] New committer announcement: Michael Luckey

[Connell O'Callaghan]

Excellent thank you for sharing Kenn!!!

Michael congratulations for this recognition of your contributions to
advancing BEAM

On Wed, Feb 27, 2019 at 11:52 AM Kenneth Knowles  wrote:

> Hi all,
>
> Please join me and the rest of the Beam PMC in welcoming a new committer:
> Michael Luckey
>
> Michael has been contributing to Beam since early 2017. He has fixed many
> build and developer environment issues, noted and root-caused breakages on
> master, generously reviewed many others' changes to the build. In
> consideration of Michael's contributions, the Beam PMC trusts Michael with
> the responsibilities of a Beam committer [1].
>
> Thank you, Michael, for your contributions.
>
> Kenn
>
> [1] https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-
> committer
>

Re: New contributor

[Connell O'Callaghan]

Welcome!!!

On Mon, Feb 4, 2019 at 3:22 PM Rui Wang  wrote:

> Welcome!
>
> -Rui
>
> On Mon, Feb 4, 2019 at 3:20 PM Ahmet Altay  wrote:
>
>> Welcome!
>>
>> On Wed, Jan 30, 2019 at 12:02 PM Kenneth Knowles  wrote:
>>
>>> Done. Welcome!
>>>
>>> On Wed, Jan 30, 2019 at 10:34 AM Bharath Kumara Subramanian <
>>> codin.mart...@gmail.com> wrote:
>>>
 Hi,
 I would like to contribute to beam and start picking up tickets.
 Can you please add me to the beam project in JIRA?

 username: bharathkk

 Thanks,
 Bharath

>>>

Re: Another new contributor!

[Connell O'Callaghan]

Welcome on board Brian!

On Wed, Jan 30, 2019 at 5:29 PM Ahmet Altay  wrote:

> Welcome Brian!
>
> On Wed, Jan 30, 2019 at 5:26 PM Brian Hulette  wrote:
>
>> Hi everyone,
>> I'm Brian Hulette, I just switched roles at Google and I'll be
>> contributing to Beam Portability as part of my new position. For now I'm
>> just going through documentation and getting familiar with Beam from the
>> user perspective, so if anything I'll just be suggesting minor edits to
>> documentation, but I hope to be putting up PRs soon enough.
>>
>> I am also an Apache committer (bhulette is my ASF id and Jira username).
>> I worked on the Arrow project's Javascript implementation in a previous
>> job, and I'm really excited to look for ways to use Arrow and Beam together
>> once I've ramped up.
>>
>> Brian
>>
>

Re: Enforce javadoc comments in public methods?

[Connell O'Callaghan]

+1

On Mon, Jan 7, 2019 at 5:22 PM Udi Meiri  wrote:

> +1
>
> On Mon, Jan 7, 2019 at 4:49 PM Daniel Oliveira 
> wrote:
>
>> +1
>>
>> I like this idea, especially with the line number requirement. The exact
>> number of lines is debatable, but you could go as low as 10 lines and that
>> would exclude any trivial setters and getters. Even better might be if it's
>> possible to configure checkstyle to ignore this for getters and setters (I
>> don't know if checkstyle supports this, but I know that other tools are
>> able to auto-detect getters and setters).
>>
>> I'm not dead-set against having annotation to suppress the comment, but
>> it carries the risk that code will be left un-commented because both the
>> dev and reviewer think it's self-explanatory, and then someone new to the
>> codebase finds it confusing.
>>
>> On Mon, Jan 7, 2019 at 11:31 AM Ankur Goenka  wrote:
>>
>>> I think it makes sense.
>>> Having an annotation to suppress this check for a method/class instead
>>> of adding trivial comment would be useful.
>>>
>>> On Mon, Jan 7, 2019 at 9:53 AM Ruoyun Huang  wrote:
>>>
 Yeah. Agree there is no reason to enforce anything for trivial methods
 like setter/getter.

 What I meant is to enforce only for a method that is *BOTH* 1) public
 method 2) has longer than N lines.

 sorry for not making the proposal clear enough in the original message,
 it should've better titled "enforce ... on non-trivial public methods".



 On Mon, Jan 7, 2019 at 1:31 AM Robert Bradshaw 
 wrote:

> IMHO, requiring comments on trivial methods like setters and getters
> is often a net negative, but setting some standard could be useful.
>
> On Mon, Jan 7, 2019 at 7:35 AM Jean-Baptiste Onofré 
> wrote:
> >
> > Hi,
> >
> > for the presence of a comment on public method, it's a good idea.
> Now,
> > about the number of lines, not sure it's a good idea. I'm thinking
> about
> > the getter/setter which are public. Most of the time, the comment is
> > pretty simple (and useless ;)).
> >
> > Regards
> > JB
> >
> > On 07/01/2019 04:35, Ruoyun Huang wrote:
> > > Hi, everyone,
> > >
> > >
> > > We were wondering whether it is a good idea to make checkstyle
> > > enforce public method comments. Our current behavior of JavaDoc
> check is:
> > >
> > >  1.
> > >
> > > Missing Class javadoc comment is reported as error.
> > >
> > >  2.
> > >
> > > Method comment missing is explicitly allowed. see [1].  It is
> not
> > > even shown as warning.
> > >
> > >  3.
> > >
> > > The actual javadoc target gives warning when certain tags are
> > > missing in javadoc, but not if the whole comment is missing.
> > >
> > >
> > >How about we enforce method comments for **1) public method and
> 2)
> > > method that is longer than N lines**. (N=~30 seems a good number,
> > > leading to ~50 violations in current repository). I can find out
> the
> > > corresponding contributors to fill in the missing comments, before
> we
> > > turning the check fully on.
> > >
> > >
> > >One caveat though is that we might want skip this check on test
> code,
> > > but I am not sure yet if our current setup can easily handle
> separated
> > > rules for main code versus test code.
> > >
> > >
> > > Is this a good idea?  Thoughts and suggestions?
> > >
> > >
> > > [1]
> > >
> https://github.com/apache/beam/blame/5ceffb246c0c38ad68dd208e951a1f39c90ef85c/sdks/java/build-tools/src/main/resources/beam/checkstyle.xml#L111
> > >
> > >
> > > Cheers,
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>


 --
 
 Ruoyun  Huang

Re: [VOTE] Release Vendored gRPC 1.13.1 v0.2, release candidate #1

[Connell O'Callaghan]

+1

On Fri, Dec 21, 2018 at 9:02 AM Thomas Weise  wrote:

> +1
>
>
> On Fri, Dec 21, 2018 at 5:00 AM Robert Bradshaw 
> wrote:
>
>> +1, let's get this out.
>>
>> We can decide about 2.9.1 later.
>> On Fri, Dec 21, 2018 at 10:43 AM Maximilian Michels 
>> wrote:
>> >
>> > +1
>> >
>> > On 20.12.18 23:11, Tyler Akidau wrote:
>> > > +1, Approve the release.
>> > >
>> > > -Tyler
>> > >
>> > > On Thu, Dec 20, 2018 at 9:49 AM Ahmet Altay > > > > wrote:
>> > >
>> > > I meant BEAM-6249 in my last sentence. It should read: "BEAM-6249
>> has a
>> > > comment about user building the libraries themselves, I am not
>> sure if they
>> > > are using the release 2.9 version directly or not."
>> > >
>> > > On Thu, Dec 20, 2018 at 9:48 AM Ahmet Altay > > > > wrote:
>> > >
>> > > +1
>> > >
>> > > I don't think there is a need for a hotfix release. The
>> reason the
>> > > initial vendoring PR (
>> https://github.com/apache/beam/pull/7024) that
>> > > started the issue was not cherry picked to the release
>> branch. BEAM-6056
>> > > has a comment about user building the libraries themselves, I
>> am not
>> > > sure if they are using the release 2.9 version directly or
>> not.
>> > >
>> > > On Thu, Dec 20, 2018 at 9:37 AM Kenneth Knowles <
>> k...@google.com
>> > > > wrote:
>> > >
>> > > I don't know yet about 2.9.1. There's a bit more context
>> on BEAM-6249.
>> > >
>> > > Kenn
>> > >
>> > > [1] https://issues.apache.org/jira/browse/BEAM-6249
>> > >
>> > > On Thu, Dec 20, 2018 at 12:02 PM Scott Wegner <
>> sc...@apache.org
>> > > > wrote:
>> > >
>> > > Releasing new vendored artifacts won't generally
>> imply a full
>> > > Beam release. The plan is to pick up the new artifact
>> version at
>> > > HEAD which will roll into the next release.
>> > >
>> > > For this particularly case, the question is if the
>> Dataflow
>> > > issue that this fixes (BEAM-6056) warrants a hotfix
>> release
>> > > (2.9.1). I don't know the answer--  Ahmet/Kenn do you
>> have any
>> > > thoughts?
>> > >
>> > > On Thu, Dec 20, 2018 at 2:18 AM Ismaël Mejía <
>> ieme...@gmail.com
>> > > > wrote:
>> > >
>> > > Does this imply that we need a subsequent full
>> release
>> > > afterwards?
>> > > I am assuming this new release is related to the
>> reported
>> > > issues with
>> > > the dataflow worker or is this something
>> different?
>> > >
>> > > On Thu, Dec 20, 2018 at 2:51 AM Kenneth Knowles
>> > > mailto:k...@apache.org>> wrote:
>> > >  >
>> > >  > +1
>> > >  >
>> > >  >  - sigs good
>> > >  >  - `jar tf` looks good
>> > >  >
>> > >  > On Wed, Dec 19, 2018 at 7:54 PM Scott Wegner
>> > > mailto:sweg...@google.com>>
>> wrote:
>> > >  >>
>> > >  >> Please review and vote on the release
>> candidate #1 for
>> > > the vendored artifact gRPC 1.13.1 v0.2
>> > >  >> [ ] +1, Approve the release
>> > >  >> [ ] -1, Do not approve the release (please
>> provide
>> > > specific comments)
>> > >  >>
>> > >  >> This is a follow-up to the previous thread
>> about
>> > > vendoring updates [1]
>> > >  >>
>> > >  >> The complete staging area is available for
>> your review,
>> > > which includes:
>> > >  >> * all artifacts to be deployed to the Maven
>> Central
>> > > Repository [2],
>> > >  >> * commit hash
>> "3b8abca3ca3352e6bf20e059f17324049a2eae0a"
>> > > [3],
>> > >  >> * artifacts which are signed with the key
>> with fingerprint
>> > >  >> 5F47BD54C52008007288FF4D3593BA6C25ABF71F [4]
>> > >  >>
>> > >  >> The vote will be open for at least 72 hours.
>> It is
>> > > adopted by majority approval, with at least 3 PMC
>> > > affirmative votes.
>> > >  >>
>> > >  >> Thanks,
>> > >  >> Scott
>> > >  >>
>> > >  >> [1]
>> > >
>> 

Re: [ANNOUNCE] Apache Beam 2.9.0 released!

[Connell O'Callaghan]

Excellent thank you Chamikara and all who contributed to this release!!!

On Thu, Dec 13, 2018 at 7:42 PM Chamikara Jayalath 
wrote:

> The Apache Beam team is pleased to announce the release of version 2.9.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 the following major new features & improvements.
> Please see the blog post for more details:
> https://beam.apache.org/blog/2018/12/13/beam-2.9.0.html
>
> Thanks to everyone who contributed to this release, and we hope you enjoy
> using Beam 2.9.0.
> -- Chamikara Jayalath, on behalf of The Apache Beam team
>

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

[Connell O'Callaghan]

+1 thank you Cham!!!

On Tue, Dec 11, 2018 at 3:14 PM Ahmet Altay  wrote:

> +1, thank you Cham!
>
> On Tue, Dec 11, 2018 at 11:09 AM Chamikara Jayalath 
> wrote:
>
>> Hi All,
>>
>> I ran Beam RC verification script [1] and updated the validation
>> spreadsheet [2]. I think the current release candidate looks good.
>>
>> So +1 for the release.
>>
>> Thanks,
>> Cham
>>
>> [1]
>> https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh
>> [2]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=2053422529
>>
>> On Fri, Dec 7, 2018 at 7:19 AM Ismaël Mejía  wrote:
>>
>>> Looking at the dates on the Spark runner git log there was a PR merged
>>> to change Spark translation from classes to URNs. I cannot see how this can
>>> impact performance. Looking at the other queries in the dashboards, there
>>> seems to be a great variability in the executions of the Spark runner to
>>> the point of feeling we don't have guarantees anymore. I wonder if this was
>>> because of other loads shared in the server(s), or because our sample is
>>> too small for the standard deviation.
>>>
>>> I would proceed with the release, the real question is if we can somehow
>>> constraint the execution of this tests to have a more consistent output.
>>>
>>>
>>> On Fri, Dec 7, 2018 at 4:10 PM Etienne Chauchot 
>>> wrote:
>>>
 Hi all,
 Regarding query7 in spark:
 - there doesn't seem to be a functional regression: query passes and
 output size is still the same

 - Also the performance degradation seems to be only on spark, the other
 runners do not seem to suffer from it.

 - performance degradation seems to be constant from 11/12 so we can
 eliminate temporary load on the jenkins server that would generate delays
 in Max transform.

 => query7 uses Max transform, fanout and side inputs, has one of these
 parts recently (11/12/18) changed in spark?

 Etienne

 Le jeudi 06 décembre 2018 à 21:32 -0800, Chamikara Jayalath a écrit :

 Udi or anybody else who is familiar about Nexmark,  please -1 the vote
 thread if you think this particular performance regression for Spark/Direct
 runners is a blocker. Otherwise I think we can continue the vote.

 Thanks,
 Cham

 On Thu, Dec 6, 2018 at 6:19 PM Chamikara Jayalath 
 wrote:

 Are either of these regressions due to known issues ? If not should
 they be considered release blockers ?

 Thanks,
 Cham

 On Thu, Dec 6, 2018 at 6:11 PM Udi Meiri  wrote:

 For DirectRunner there are regressions in query 7 sql direct runner
 batch mode
 
  (2x)
 and streaming mode (5x).


 On Thu, Dec 6, 2018 at 5:59 PM Udi Meiri  wrote:

 I see a regression for query 7 spark runner batch mode
 
  on
 about 2018-11-13.
 [image: image.png]

 On Thu, Dec 6, 2018 at 2:46 AM Chamikara Jayalath 
 wrote:

 Hi everyone,

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


 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 EEAC70DF3D0BC23B
  [3],
 * all artifacts to be deployed to the Maven Central Repository [4],
 * source code tag "v2.9.0-RC1" [5],
 * website pull request listing the release [6] and publishing the API
 reference manual [7].
 * Python artifacts are deployed along with the source release to the
 dist.apache.org [2].
 * Validation sheet with a tab for 2.9.0 release to help with
 validation [7].

 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=12344258
 [2] https://dist.apache.org/repos/dist/dev/beam/2.9.0/
 [3] https://dist.apache.org/repos/dist/release/beam/KEYS
 [4]
 https://repository.apache.org/content/repositories/orgapachebeam-1054/
 [5] https://github.com/apache/beam/tree/v2.9.0-RC1
 [6] https://github.com/apache/beam/pull/7215
 [7] https://github.com/apache/beam-site/pull/584
 [8]
 https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=2053422529

Re: [VOTE] Mark 2.7.0 branch as a long term support (LTS) branch

[Connell O'Callaghan]

+1

On Fri, Nov 9, 2018 at 11:06 PM Manu Zhang  wrote:

> +1
>
> Thanks,
> Manu Zhang
> On Nov 10, 2018, 12:55 PM +0800, Kenneth Knowles , wrote:
>
> +1
>
> On Fri, Nov 9, 2018, 12:04 Scott Wegner 
>> +1 Thanks for driving this Ahmet!
>>
>> On Fri, Nov 9, 2018 at 9:33 AM Chamikara Jayalath 
>> wrote:
>>
>>> +1
>>>
>>> Thanks,
>>> Cham
>>>
>>> On Fri, Nov 9, 2018 at 9:31 AM Udi Meiri  wrote:
>>>
 +1

 On Fri, Nov 9, 2018 at 8:31 AM Maximilian Michels 
 wrote:

> +1
>
> On 09.11.18 09:38, Robert Bradshaw wrote:
> > +1 approve.
> > On Fri, Nov 9, 2018 at 2:47 AM Ahmet Altay  wrote:
> >>
> >> Hi all,
> >>
> >> Please review the following statement:
> >>
> >> "2.7.0 branch will be marked as the long-term-support (LTS) release
> branch. This branch will be supported for a window of 6 months starting
> from the day it is marked as an LTS branch. Beam community will decide on
> which issues will be backported and when patch releases on the branch will
> be made on a case by case basis.
> >>
> >> [ ] +1, Approve
> >> [ ] -1, Do not approve (please provide specific comments)
> >>
> >> Context:
> >> - Discussion on the dev@ list [1].
> >> - Beam's release policies [2].
> >>
> >> Thank you,
> >> Ahmet
> >>
> >> [1]
> https://lists.apache.org/thread.html/f604b2d688ad467ddccd4cf56b664b7309dae78f1bd8849e4bb9aae2@%3Cdev.beam.apache.org%3E
> >> [2] https://beam.apache.org/community/policies/
> >>
> >>
> >>
>

>>
>> --
>>
>>
>>
>>
>> Got feedback? tinyurl.com/swegner-feedback
>>
>

Re: Tracking and resolving release blocking bugs

[Connell O'Callaghan]

Ismaël and Ahmet thank you both for your responses!!!

Can the text on the site today - reproduced below - be enhanced with the
text in bold? Note I would not expect this new text to be in bold once
deployed to the site.
Triage release-blocking issues in JIRA

There could be outstanding release-blocking issues, which should be triaged
before proceeding to build a release candidate. We track them by assigning
a specific Fix version field even before the issue resolved.

The list of release-blocking issues is available at the version status page
<https://issues.apache.org/jira/browse/BEAM/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel>.
Triage each unresolved issue with one of the following resolutions:

   - If the issue has been resolved and JIRA was not updated, resolve it
   accordingly.
   - If the issue has not been resolved and it is acceptable to defer this
   until the next release, update the Fix Version field to the new version
   you just created. Please consider discussing this with stakeholders and the
   dev@ mailing list, as appropriate.
   - If the issue has not been resolved and it is not acceptable to release
   until it is fixed, the release cannot proceed. Instead, work with the Beam
   community to resolve the issue.

*If there is a bug found in the RC creation process/tools, those issues
should be considered high priority and fixed in 7 days. *

This is to prevent a regression in the amount of time it takes to cut an RC.


On Fri, Sep 21, 2018 at 2:06 PM Ahmet Altay  wrote:

> I agree with Ismaël, this process is generally working well. As an
> improvement we could document it somewhere.
>
> One other area I think we can improve is, issues that are related to the
> release process. For example, at times we will have issues that require
> doing additional manual steps in the release process, we will file a JIRA
> and we tend to punt those JIRAs release after release as long as there is a
> manual work around. However, these issues add to the cost of cutting
> releases. I would propose prioritizing those issues that are identified
> during the release and about the release process itself.
>
> Ahmet
>
> On Wed, Sep 19, 2018 at 4:41 AM, Ismaël Mejía  wrote:
>
>> We have done this so far by letting the JIRA issues 'Open' with the
>> 'Fix version' corresponding to the upcoming release and we track the
>> progress between the branch cut and the first release candidate with
>> the assigned parties, the process has been the de-facto standard since
>> long time ago and has worked so far smoothly. More info here:
>>
>>
>> https://beam.apache.org/contribute/release-guide/#triage-release-blocking-issues-in-jira
>>
>> Is there something missing? or do you have other ideas maybe to
>> improve it in mind?
>>
>> On Wed, Sep 19, 2018 at 2:34 AM Connell O'Callaghan 
>> wrote:
>> >
>> > Hi All
>> >
>> > In order to allow successful and smooth deployment of the latest BEAM
>> releases, are the community OK that we track bugs blocking releases, with a
>> goal to resolve such bugs within a week? If there is general agreement (or
>> no major objections) on this we will edit the contributor page using
>> similar language to the "Stale pull requests" section -early next week.
>> >
>> > Thank you all,
>> > - Connell
>>
>
>

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

[Connell O'Callaghan]

+1 to Thomas's suggestion - if Charles or others cannot reproduce.

On Thu, Sep 20, 2018 at 2:40 PM Thomas Weise  wrote:

> We can also consider releasing 2.7.0 and then follow up with 2.7.1 if the
> problem can be reproduced and requires a fix. Just food for thought :)
>
>
> On Thu, Sep 20, 2018 at 2:13 PM Charles Chen  wrote:
>
>> My mistake, it looks like the correct beam staging repository (
>> https://repository.apache.org/content/repositories/orgapachebeam-1046/)
>> is specified in your pom file.
>>
>> On Thu, Sep 20, 2018 at 2:10 PM Charles Chen  wrote:
>>
>>> Hey Romain and JB, do you have any progress on this?  One thing I would
>>> like to point out is that 2.7.0 isn't yet pushed to Maven Central, so
>>> referring to it by version is not expected to work (and it looks like this
>>> is what is done in your repo:
>>> https://github.com/rmannibucau/beam-2.7.0-fails).  Luke indicated above
>>> that he doesn't see any dependency changes.  Can you isolate and reproduce
>>> this problem so that we can develop a fix, if necessary?  I would like to
>>> proceed with an RC2 as soon as possible.
>>>
>>> On Wed, Sep 19, 2018 at 6:37 AM Romain Manni-Bucau <
>>> rmannibu...@gmail.com> wrote:
>>>
 Quick update on the spark issue: I didn't get enough time to identify
 it clearly but managed to have a passing run of my test changing a bunch of
 versions.
 I suspect my code triggers some class conflicting between spark and my
 shade leading to a serialization issue. I didn't test userClassPathFirst
 option of spark but it can be an interesting thing to enable in beam 
 runner.
 However it is still very confusing to have it not running just
 upgrading beam version and the spark error is very hard to understand.

 Romain Manni-Bucau
 @rmannibucau  |  Blog
  | Old Blog
  | Github
  | LinkedIn
  | Book
 


 Le mar. 18 sept. 2018 à 20:17, Lukasz Cwik  a écrit :

> Romain hinted that this was a dependency issue but when comparing the
> two dependency trees I don't get much of a difference:
>
> lcwik@lcwik0: ~$ diff /tmp/260 /tmp/270
> < [INFO] +- org.apache.beam:beam-runners-spark:jar:2.6.0:compile
> < [INFO] |  +- org.apache.beam:beam-model-pipeline:jar:2.6.0:compile
> ---
> > [INFO] +- org.apache.beam:beam-runners-spark:jar:2.7.0:compile
> > [INFO] |  +- org.apache.beam:beam-model-pipeline:jar:2.7.0:compile
> 5c6
> < [INFO] |  +- org.apache.beam:beam-sdks-java-core:jar:2.6.0:compile
> ---
> > [INFO] |  +- org.apache.beam:beam-sdks-java-core:jar:2.7.0:compile
> 14,18c15,19
> < [INFO] |  |  \- org.tukaani:xz:jar:1.5:compile
> < [INFO] |  +-
> org.apache.beam:beam-runners-core-construction-java:jar:2.6.0:compile
> < [INFO] |  |  \-
> org.apache.beam:beam-model-job-management:jar:2.6.0:compile
> < [INFO] |  +- org.apache.beam:beam-runners-core-java:jar:2.6.0:compile
> < [INFO] |  |  \-
> org.apache.beam:beam-model-fn-execution:jar:2.6.0:compile
> ---
> > [INFO] |  |  \- org.tukaani:xz:jar:1.8:compile
> > [INFO] |  +-
> org.apache.beam:beam-runners-core-construction-java:jar:2.7.0:compile
> > [INFO] |  |  \-
> org.apache.beam:beam-model-job-management:jar:2.7.0:compile
> > [INFO] |  +- org.apache.beam:beam-runners-core-java:jar:2.7.0:compile
> > [INFO] |  |  \-
> org.apache.beam:beam-model-fn-execution:jar:2.7.0:compile
>
> Other then Beam package changes, the only other change is xz which I
> don't believe could be causing the issue.
>
> On Tue, Sep 18, 2018 at 8:38 AM Jean-Baptiste Onofré 
> wrote:
>
>> Thanks, let me take a look.
>>
>> Regards
>> JB
>>
>> On 18/09/2018 17:36, Romain Manni-Bucau wrote:
>> >
>> >
>> >
>> > Le mar. 18 sept. 2018 à 16:44, Jean-Baptiste Onofré <
>> j...@nanthrax.net
>> > > a écrit :
>> >
>> > Hi,
>> >
>> > I don't have the issue ;)
>> >
>> > As said in my vote, I tested 2.7.0 RC1 on beam-samples with
>> Spark
>> > without problem.
>> >
>> > I don't reproduce Romain issue as well.
>> >
>> > @Romain can you provide some details to reproduce the issue ?
>> >
>> >
>> > Sure, you can use this
>> > reproducer: https://github.com/rmannibucau/beam-2.7.0-fails
>> > It shows that it suceeds on 2.6 and fails on 2.7.
>> >
>> >
>> >
>> > Regards
>> > JB
>> >
>> > On 17/09/2018 19:17, Charles Chen wrote:
>> > > Luke, Maximillian, Raghu, can you please propose cherry-pick
>> PRs
>> > to the
>> > > 

Tracking and resolving release blocking bugs

[Connell O'Callaghan]

Hi All

In order to allow successful and smooth deployment of the latest BEAM
releases, are the community OK that we track bugs blocking releases, with a
goal to resolve such bugs within a week? If there is general agreement (or
no major objections) on this we will edit the contributor page using
similar language to the "Stale pull requests" section -early next week.

Thank you all,
- Connell

Re: Beam dashboards

[Connell O'Callaghan]

Thank you Mikhail for sharing this and to everyone involved in these
improvements!!! It will be great to hear about progress and any blockers
encountered with this work.

On Thu, Sep 13, 2018 at 11:12 AM Mikhail Gryzykhin 
wrote:

> Hi everyone,
>
> Huygaa and me are working on creating dashboards for Beam.
>
> So far I created a POC dashboard for post-commit greenness
>  that includes a
> list of latest failed jobs and dashboard for pre-commits
>  duration, that one
> contains only duration so far.
>
> We have work ongoing for adding github statistics.
>
> Please, check those out. Any feedback is welcome.
>
> Small hints:
> * You can change time range you're looking at in to-right corner.
> * You can choose dashboard by clicking dashboard name on top-left corner.
>
> As a short insight:
> Thank you everyone who helps fixing post-commit tests flakes. We moved
> from ~30% to 75-85% successful runs.
>
> Best regards,
> --Mikhail
>
> Have feedback ?
>

JIRA permissions request

[Connell O'Callaghan]

Hi dev@,

There are quite a few efforts in flight that have a lot of identified work
that needs a bit of project management to better communicate what is being
worked on and in what order across the community -- Portability framework,
portable runners, and SQL being examples that come to mind. Rafael,
Henning, and I want to work with JIRA's tools to produce (and publish) the
necessary dashboards, reports, and views. We appear to be unable to share
dashboards we create with the entire project due to a lack of permissions.
Can someone explain to us how we can create and then share them? Otherwise,
if it's just a permissions issue, is it possible to be given the necessary
permissions?

Thank you in advance,
- Connell

Re: Test set fails: beam_PostCommit_Python_PortableValidatesRunner_Flink_Gradle

[Connell O'Callaghan]

Thank you both for addressing failing tests.

On Wed, Sep 5, 2018, 10:05 AM Thomas Weise  wrote:

> I will take a look. I know that still 2 tests fail in streaming mode that
> need to be investigated and fixed. Will create a ticket with more context.
>
> --
> sent from mobile
>
> On Wed, Sep 5, 2018, 6:59 PM Mikhail Gryzykhin  wrote:
>
>> Hi everyone,
>>
>> We have added beam_PostCommit_Python_PortableValidatesRunner_Flink_Gradle
>> 
>> job to Jenkins several days ago. However all of its runs have failed so far.
>>
>> Are we working on the fix, or can we disable this job to remove bad
>> signal?
>>
>> Thank you,
>> --Mikhail
>>
>> Have feedback ?
>>
>>

Re: Beam Schemas: current status

[Connell O'Callaghan]

Nice work Reuven!!!

On Thu, Aug 30, 2018 at 6:57 AM Jean-Baptiste Onofré 
wrote:

> Nice feature, thanks Reuven !
>
> I started to revamp the Spark runner with dataset, I will leverage this !
>
> Regards
> JB
>
> On 29/08/2018 07:40, Reuven Lax wrote:
> > I wanted to send a quick note to the community about the current status
> > of schema-aware PCollections in Beam. As some might remember we had a
> > good discussion last year about the design of these schemas, involving
> > many folks from different parts of the community. I sent a summary
> > earlier this year explaining how schemas has been integrated into the
> > DoFn framework. Much has happened since then, and here are some of the
> > highlights.
> >
> >
> > First, I want to emphasize that all the schema-aware classes are
> > currently marked @Experimental. Nothing is set in stone yet, so if you
> > have questions about any decisions made, please start a discussion!
> >
> >
> >   SQL
> >
> > The first big milestone for schemas was porting all of BeamSQL to use
> > the framework, which was done in pr/5956. This was a lot of work,
> > exposed many bugs in the schema implementation, but now provides great
> > evidence that schemas work!
> >
> >
> >   Schema inference
> >
> > Beam can automatically infer schemas from Java POJOs (objects with
> > public fields) or JavaBean objects (objects with getter/setter methods).
> > Often you can do this by simply annotating the class. For example:
> >
> >
> > @DefaultSchema(JavaFieldSchema.class)
> >
> > publicclassUserEvent{
> >
> >  publicStringuserId;
> >
> >  publicLatLonglocation;
> >
> >  PublicStringcountryCode;
> >
> >  publiclongtransactionCost;
> >
> >  publicdoubletransactionDuration;
> >
> >  publicListtraceMessages;
> >
> > };
> >
> >
> > @DefaultSchema(JavaFieldSchema.class)
> >
> > publicclassLatLong{
> >
> >  publicdoublelatitude;
> >
> >  publicdoublelongitude;
> >
> > }
> >
> >
> > Beam will automatically infer schemas for these classes! So if you have
> > a PCollection, it will automatically get the following schema:
> >
> >
> > UserEvent:
> >
> >  userId: STRING
> >
> >  location: ROW(LatLong)
> >
> >  countryCode: STRING
> >
> >  transactionCost: INT64
> >
> >  transactionDuration: DOUBLE
> >
> >  traceMessages: ARRAY[STRING]]
> >
> >
> > LatLong:
> >
> >  latitude: DOUBLE
> >
> >  longitude: DOUBLE
> >
> >
> > Now it’s not always possible to annotate the class like this (you may
> > not own the class definition), so you can also explicitly register this
> > using Pipeline:getSchemaRegistry:registerPOJO, and the same for
> JavaBeans.
> >
> >
> >   Coders
> >
> > Beam has a built-in coder for any schema-aware PCollection, largely
> > removing the need for users to care about coders. We generate low-level
> > bytecode (using ByteBuddy) to implement the coder for each schema, so
> > these coders are quite performant. This provides a better default coder
> > for Java POJO objects as well. In the past users were recommended to use
> > AvroCoder for pojos, which many have found inefficient. Now there’s a
> > more-efficient solution.
> >
> >
> >   Utility Transforms
> >
> > Schemas are already useful for implementers of extensions such as SQL,
> > but the goal was to use them to make Beam itself easier to use. To this
> > end, I’ve been implementing a library of transforms that allow for easy
> > manipulation of schema PCollections. So far Filter and Select are
> > merged, Group is about to go out for review (it needs some more javadoc
> > and unit tests), and Join is being developed but doesn’t yet have a
> > final interface.
> >
> >
> > Filter
> >
> > Given a PCollection, I want to keep only those in an area of
> > southern manhattan. Well this is easy!
> >
> >
> > PCollectionmanhattanEvents =allEvents.apply(Filter
> >
> >  .whereFieldName("latitude",lat ->lat <40.720& >40.699)
> >
> >  .whereFieldName("longitude",long->long<-73.969&>-74.747));
> >
> >
> > Schemas along with lambdas allows us to write this transform
> > declaratively. The Filter transform also allows you to register filter
> > functions that operate on multiple fields at the same time.
> >
> >
> > Select
> >
> > Let’s say that I don’t need all the fields in a row. For instance, I’m
> > only interested in the userId and traceMessages, and don’t care about
> > the location. In that case I can write the following:
> >
> >
> > PCollectionselected
> > =allEvents.apply(Select.fieldNames(“userId”,“traceMessages”));
> >
> >
> > BTW, Beam also keeps track of which fields are accessed by a transform
> > In the future we can automatically insert Selects in front of subgraphs
> > to drop fields that are not referenced in that subgraph.
> >
> >
> > Group
> >
> > Group is one of the more advanced transforms. In its most basic form, it
> > provides a convenient way to group by key:
> >
> >
> > PCollection>byUserAndCountry =
> >
> >allEvents.apply(Group.byFieldNames(“userId”,“countryCode”));
> >
> >
> > Notice how much more 

Re: Beam Docs Contributor

[Connell O'Callaghan]

Welcome Rose!!!

On Tue, Aug 21, 2018 at 12:57 AM Maximilian Michels  wrote:

> That sounds great, Rose. Welcome!
>
> On 21.08.18 09:21, Etienne Chauchot wrote:
> > Welcome Rose !
> >
> > Etienne
> >
> > Le lundi 30 juillet 2018 à 10:10 -0700, Thomas Weise a écrit :
> >> Welcome Rose, and looking forward to the docs update!
> >>
> >> On Mon, Jul 30, 2018 at 9:15 AM Henning Rohde  >> > wrote:
> >>> Welcome Rose! Great to have you here.
> >>>
> >>> On Mon, Jul 30, 2018 at 2:23 AM Ismaël Mejía  >>> > wrote:
>  Welcome !
>  Great to see someone new working in this important area for the
> project.
> 
> 
>  On Mon, Jul 30, 2018 at 5:57 AM Kai Jiang   > wrote:
> > Welcome Rose!
> > ᐧ
> >
> > On Sun, Jul 29, 2018 at 8:53 PM Rui Wang  > > wrote:
> >> Welcome!
> >>
> >> -Rui
> >>
> >> On Sun, Jul 29, 2018 at 7:07 PM Griselda Cuevas  >> > wrote:
> >>> Welcome Rose, very glad to have you in the community :)
> >>>
> >>>
> >>>
> >>> On Fri, 27 Jul 2018 at 16:29, Ahmet Altay  >>> > wrote:
>  Welcome Rose! Looking forward to your contributions.
> 
>  On Fri, Jul 27, 2018 at 4:08 PM, Rose Nguyen
>  mailto:rtngu...@google.com>> wrote:
> > Hi all:
> >
> > I'm Rose! I've worked on Cloud Dataflow documentation and now
> > I'm starting a project to refresh the Beam docs and improve the
> > onboarding experience. We're planning on splitting up the
> > programming guide into multiple pages, making the docs more
> > accessible for new users. I've got lots of ideas for doc
> > improvements, some of which are motivated by the UX research,
> > and am excited to share them with you all and work on them.
> >
> > I look forward to interacting with everybody in the community.
> > I welcome comments, thoughts, feedback, etc.
> > --
> >
> >
> >
> >
> > Rose Thi Nguyen
> >
> >   Technical Writer
> >
> > (281) 683-6900
> >
> 
>

Re: [PROPOSAL] Prepare Beam 2.7.0 release

[Connell O'Callaghan]

+1 Charles thank you for taking this up and helping us maintain this
schedule.

On Mon, Aug 20, 2018 at 11:29 AM Charles Chen  wrote:

> Hey everyone,
>
> Our release calendar indicates that the process for the 2.7.0 Beam release
> should start on September 7.
>
> I volunteer to perform this release and propose the following schedule:
>
>- We start triaging issues in JIRA this week.
>- I will cut the initial 2.7.0 release branch on September 7.
>- After September 7, any blockers will need to be manually
>cherry-picked into the release branch.
>- After tests pass and blockers are fully addressed, I will move on
>and perform other release tasks.
>
> What do you think?
>
> Best,
> Charles
>

Re: [ANNOUNCE] Apache Beam 2.6.0 released!

[Connell O'Callaghan]

Pablo and all involved thank you for working to get this release
completed!!!

On Thu, Aug 9, 2018 at 3:06 PM Pablo Estrada  wrote:

> Of course, I messed that link up again. The release notes should be here:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12343392
>
> On Thu, Aug 9, 2018 at 10:11 AM Pablo Estrada  wrote:
>
>> As was pointed out to me by Ryan Williams, the link I posted with the
>> release notes is not right. Here is a link with Beam 2.6.0 release notes
>> for those interested:
>>
>> https://issues.apache.org/jira/projects/BEAM/versions/12343392
>>
>> On Thu, Aug 9, 2018 at 9:41 AM Alexey Romanenko 
>> wrote:
>>
>>> Great news!
>>> Thanks to Pablo for driving this and to all contributors of this release!
>>>
>>>
>>> On 9 Aug 2018, at 00:48, Pablo Estrada  wrote:
>>>
>>> The Apache Beam team is pleased to announce the release of 2.6.0
>>> version!
>>>
>>> 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 the following major new features & improvements,
>>> among others:
>>> - Improvements for internal Context Management in Python SDK
>>> - A number of improvements to the Portability Framework
>>> - A Universal Local Runner has been added to Beam. This runner runs in a
>>> single machine using portability, and containerized SDK harnesses.
>>> - Increased the coverage of ErrorProne analysis of the codebase.
>>> - Updates to various dependency versions
>>> - Updates to stability, performance, and documentation.
>>> - SQL - improvements: support exists operator, implemented sum()
>>> aggregations, fixes to CASE expression, support for date comparison,
>>> support LIMIT on Unbounded Data
>>> - Provide automatic schema registration for POJOs
>>>
>>> You can take a look at the Release Notes for more details:
>>>
>>> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343392=12319527
>>> *
>>>
>>> Thanks to everyone who participated in this release, and we hope you'll
>>> have a good time using Beam 2.6.0.
>>> --
>>> Pablo Estrada, on behalf of The Apache Beam team
>>> --
>>> Got feedback? go/pabloem-feedback
>>> 
>>>
>>>
>>> --
>> Got feedback? go/pabloem-feedback
>> 
>>
> --
> Got feedback? go/pabloem-feedback
> 
>

Hello Beam Community!!!

[Connell O'Callaghan]

Hi All

My name is Connell. I am relatively new to Beam (and Google where I work as
a technical PM). My philosophy is very much oriented around how can I serve
the team. Hence, I am extremely interested to learn how I can help continue
the great work of this community. One particular area I am curious about is
how this community triages and manages issues. I will do some self study on
this. But I would be very interested to engage with others interested in
this general topic. Please let me know if you wish to connect on this or
other topics!!!

Thank you in advance!!!

- Connell