Re: [ANNOUNCE] New committer: Yi Hu

[Tomo Suzuki via dev]

Congratulations!

On Wed, Nov 9, 2022 at 3:00 PM John Casey via dev 
wrote:

> Congrats! this is well deserved YI
>
> On Wed, Nov 9, 2022 at 2:58 PM Austin Bennett 
> wrote:
>
>> Congrats, and Thanks, Yi!
>>
>> On Wed, Nov 9, 2022 at 11:24 AM Valentyn Tymofieiev via dev <
>> dev@beam.apache.org> wrote:
>>
>>> I am with the Beam PMC on this, congratulations and very well deserved,
>>> Yi!
>>>
>>> On Wed, Nov 9, 2022 at 11:08 AM Byron Ellis via dev 
>>> wrote:
>>>
 Congratulations!

 On Wed, Nov 9, 2022 at 11:00 AM Pablo Estrada via dev <
 dev@beam.apache.org> wrote:

> +1 thanks Yi : D
>
> On Wed, Nov 9, 2022 at 10:47 AM Danny McCormick via dev <
> dev@beam.apache.org> wrote:
>
>> Congrats Yi! I've really appreciated the ways you've consistently
>> taken responsibility for improving our team's infra and working through
>> sharp edges in the codebase that others have ignored. This is definitely
>> well deserved!
>>
>> Thanks,
>> Danny
>>
>> On Wed, Nov 9, 2022 at 1:37 PM Anand Inguva via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Congratulations Yi!
>>>
>>> On Wed, Nov 9, 2022 at 1:35 PM Ritesh Ghorse via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Congratulations Yi!

 On Wed, Nov 9, 2022 at 1:34 PM Ahmed Abualsaud via dev <
 dev@beam.apache.org> wrote:

> Congrats Yi!
>
> On Wed, Nov 9, 2022 at 1:33 PM Sachin Agarwal via dev <
> dev@beam.apache.org> wrote:
>
>> Congratulations Yi!
>>
>> On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles 
>> wrote:
>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new
>>> committer: Yi Hu (y...@apache.org)
>>>
>>> Yi started contributing to Beam in early 2022. Yi's
>>> contributions are very diverse! I/Os, performance tests, Jenkins, 
>>> support
>>> for Schema logical types. Not only code but a very large amount of 
>>> code
>>> review. Yi is also noted for picking up smaller issues that 
>>> normally would
>>> be left on the backburner and filing issues that he finds rather 
>>> than
>>> ignoring them.
>>>
>>> Considering their contributions to the project over this
>>> timeframe, the Beam PMC trusts Yi with the responsibilities of a 
>>> Beam
>>> committer. [1]
>>>
>>> Thank you Yi! And we are looking to see more of your
>>> contributions!
>>>
>>> Kenn, on behalf of the Apache Beam PMC
>>>
>>> [1]
>>>
>>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>
>>

-- 
Regards,
Tomo

Re: [Python][Bikeshed] typehint vs. type-hint vs. "type hint"

[Austin Bennett]

+1

And, well articulated, @Robert Burke  !

On Wed, Nov 9, 2022 at 10:43 AM Robert Burke  wrote:

> +1 to standardizing on "type hint"
>
> I learned that there's a rule in English that defines when one would have
> a space in a compound word or not. If removing one of the components would
> change the meaning of the others, the space should be removed.
>
> Eg. By removing "type", it's still a hint, so "type hint" is appropriate.
>
> This rule is why the Apple products are "MacBooks" or "AirPods" rather
> than "Mac Book" and "Air Pods". Without the Mac, the laptop isn't a Book.
> Without the Air, it's not a "pod".
>
>
>
> On Wed, Nov 9, 2022, 10:35 AM Kenneth Knowles  wrote:
>
>> +1 to "type hint" for referring to hinting that something has a
>> particular type, and "type" for referring to a... type.
>>
>> On Mon, Nov 7, 2022 at 7:27 AM Jack McCluskey via dev <
>> dev@beam.apache.org> wrote:
>>
>>> I'm in agreement that how we refer to type hints in documentation should
>>> be standardized across the board. It's a good practice for both style and
>>> clarity. Seems like it wouldn't be too hard to update our docstrings
>>> either, based on a quick search of the repo.
>>>
>>> On Mon, Nov 7, 2022 at 9:00 AM Brian Hulette via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Hi everyone,

 In a recent code review we noticed that we are not consistent when
 describing python type hints in documentation. Depending on who wrote the
 patch, we switch between typehint, type-hint, and "type hint" [1].

 I think we should standardize on "type hint" as this is what Guido used
 in PEP 484 [2]. Please comment on the issue in the next few days if you
 disagree with this approach.

 Note this is orthogonal to how we refer to type hints in _code_, in our
 public APIs. In general we use "type" in that context (e.g.
 `with_input_types`), and there doesn't seem to be a consistency issue.

 [1] https://github.com/apache/beam/issues/23950
 [2] https://peps.python.org/pep-0484/

>>>

Re: [ANNOUNCE] New committer: Yi Hu

[John Casey via dev]

Congrats! this is well deserved YI

On Wed, Nov 9, 2022 at 2:58 PM Austin Bennett 
wrote:

> Congrats, and Thanks, Yi!
>
> On Wed, Nov 9, 2022 at 11:24 AM Valentyn Tymofieiev via dev <
> dev@beam.apache.org> wrote:
>
>> I am with the Beam PMC on this, congratulations and very well deserved,
>> Yi!
>>
>> On Wed, Nov 9, 2022 at 11:08 AM Byron Ellis via dev 
>> wrote:
>>
>>> Congratulations!
>>>
>>> On Wed, Nov 9, 2022 at 11:00 AM Pablo Estrada via dev <
>>> dev@beam.apache.org> wrote:
>>>
 +1 thanks Yi : D

 On Wed, Nov 9, 2022 at 10:47 AM Danny McCormick via dev <
 dev@beam.apache.org> wrote:

> Congrats Yi! I've really appreciated the ways you've consistently
> taken responsibility for improving our team's infra and working through
> sharp edges in the codebase that others have ignored. This is definitely
> well deserved!
>
> Thanks,
> Danny
>
> On Wed, Nov 9, 2022 at 1:37 PM Anand Inguva via dev <
> dev@beam.apache.org> wrote:
>
>> Congratulations Yi!
>>
>> On Wed, Nov 9, 2022 at 1:35 PM Ritesh Ghorse via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Congratulations Yi!
>>>
>>> On Wed, Nov 9, 2022 at 1:34 PM Ahmed Abualsaud via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Congrats Yi!

 On Wed, Nov 9, 2022 at 1:33 PM Sachin Agarwal via dev <
 dev@beam.apache.org> wrote:

> Congratulations Yi!
>
> On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles 
> wrote:
>
>> Hi all,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new
>> committer: Yi Hu (y...@apache.org)
>>
>> Yi started contributing to Beam in early 2022. Yi's contributions
>> are very diverse! I/Os, performance tests, Jenkins, support for 
>> Schema
>> logical types. Not only code but a very large amount of code review. 
>> Yi is
>> also noted for picking up smaller issues that normally would be left 
>> on the
>> backburner and filing issues that he finds rather than ignoring them.
>>
>> Considering their contributions to the project over this
>> timeframe, the Beam PMC trusts Yi with the responsibilities of a Beam
>> committer. [1]
>>
>> Thank you Yi! And we are looking to see more of your
>> contributions!
>>
>> Kenn, on behalf of the Apache Beam PMC
>>
>> [1]
>>
>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>
>

Re: [ANNOUNCE] New committer: Yi Hu

[Austin Bennett]

Congrats, and Thanks, Yi!

On Wed, Nov 9, 2022 at 11:24 AM Valentyn Tymofieiev via dev <
dev@beam.apache.org> wrote:

> I am with the Beam PMC on this, congratulations and very well deserved, Yi!
>
> On Wed, Nov 9, 2022 at 11:08 AM Byron Ellis via dev 
> wrote:
>
>> Congratulations!
>>
>> On Wed, Nov 9, 2022 at 11:00 AM Pablo Estrada via dev <
>> dev@beam.apache.org> wrote:
>>
>>> +1 thanks Yi : D
>>>
>>> On Wed, Nov 9, 2022 at 10:47 AM Danny McCormick via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Congrats Yi! I've really appreciated the ways you've consistently taken
 responsibility for improving our team's infra and working through sharp
 edges in the codebase that others have ignored. This is definitely well
 deserved!

 Thanks,
 Danny

 On Wed, Nov 9, 2022 at 1:37 PM Anand Inguva via dev <
 dev@beam.apache.org> wrote:

> Congratulations Yi!
>
> On Wed, Nov 9, 2022 at 1:35 PM Ritesh Ghorse via dev <
> dev@beam.apache.org> wrote:
>
>> Congratulations Yi!
>>
>> On Wed, Nov 9, 2022 at 1:34 PM Ahmed Abualsaud via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Congrats Yi!
>>>
>>> On Wed, Nov 9, 2022 at 1:33 PM Sachin Agarwal via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Congratulations Yi!

 On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles 
 wrote:

> Hi all,
>
> Please join me and the rest of the Beam PMC in welcoming a new
> committer: Yi Hu (y...@apache.org)
>
> Yi started contributing to Beam in early 2022. Yi's contributions
> are very diverse! I/Os, performance tests, Jenkins, support for Schema
> logical types. Not only code but a very large amount of code review. 
> Yi is
> also noted for picking up smaller issues that normally would be left 
> on the
> backburner and filing issues that he finds rather than ignoring them.
>
> Considering their contributions to the project over this
> timeframe, the Beam PMC trusts Yi with the responsibilities of a Beam
> committer. [1]
>
> Thank you Yi! And we are looking to see more of your contributions!
>
> Kenn, on behalf of the Apache Beam PMC
>
> [1]
>
> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>

Re: [ANNOUNCE] New committer: Yi Hu

[Brian Hulette via dev]

Well deserved! Congratulations Yi

On Wed, Nov 9, 2022 at 11:25 AM Valentyn Tymofieiev via dev <
dev@beam.apache.org> wrote:

> I am with the Beam PMC on this, congratulations and very well deserved, Yi!
>
> On Wed, Nov 9, 2022 at 11:08 AM Byron Ellis via dev 
> wrote:
>
>> Congratulations!
>>
>> On Wed, Nov 9, 2022 at 11:00 AM Pablo Estrada via dev <
>> dev@beam.apache.org> wrote:
>>
>>> +1 thanks Yi : D
>>>
>>> On Wed, Nov 9, 2022 at 10:47 AM Danny McCormick via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Congrats Yi! I've really appreciated the ways you've consistently taken
 responsibility for improving our team's infra and working through sharp
 edges in the codebase that others have ignored. This is definitely well
 deserved!

 Thanks,
 Danny

 On Wed, Nov 9, 2022 at 1:37 PM Anand Inguva via dev <
 dev@beam.apache.org> wrote:

> Congratulations Yi!
>
> On Wed, Nov 9, 2022 at 1:35 PM Ritesh Ghorse via dev <
> dev@beam.apache.org> wrote:
>
>> Congratulations Yi!
>>
>> On Wed, Nov 9, 2022 at 1:34 PM Ahmed Abualsaud via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Congrats Yi!
>>>
>>> On Wed, Nov 9, 2022 at 1:33 PM Sachin Agarwal via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Congratulations Yi!

 On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles 
 wrote:

> Hi all,
>
> Please join me and the rest of the Beam PMC in welcoming a new
> committer: Yi Hu (y...@apache.org)
>
> Yi started contributing to Beam in early 2022. Yi's contributions
> are very diverse! I/Os, performance tests, Jenkins, support for Schema
> logical types. Not only code but a very large amount of code review. 
> Yi is
> also noted for picking up smaller issues that normally would be left 
> on the
> backburner and filing issues that he finds rather than ignoring them.
>
> Considering their contributions to the project over this
> timeframe, the Beam PMC trusts Yi with the responsibilities of a Beam
> committer. [1]
>
> Thank you Yi! And we are looking to see more of your contributions!
>
> Kenn, on behalf of the Apache Beam PMC
>
> [1]
>
> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>

Re: [ANNOUNCE] New committer: Yi Hu

[Valentyn Tymofieiev via dev]

I am with the Beam PMC on this, congratulations and very well deserved, Yi!

On Wed, Nov 9, 2022 at 11:08 AM Byron Ellis via dev 
wrote:

> Congratulations!
>
> On Wed, Nov 9, 2022 at 11:00 AM Pablo Estrada via dev 
> wrote:
>
>> +1 thanks Yi : D
>>
>> On Wed, Nov 9, 2022 at 10:47 AM Danny McCormick via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Congrats Yi! I've really appreciated the ways you've consistently taken
>>> responsibility for improving our team's infra and working through sharp
>>> edges in the codebase that others have ignored. This is definitely well
>>> deserved!
>>>
>>> Thanks,
>>> Danny
>>>
>>> On Wed, Nov 9, 2022 at 1:37 PM Anand Inguva via dev 
>>> wrote:
>>>
 Congratulations Yi!

 On Wed, Nov 9, 2022 at 1:35 PM Ritesh Ghorse via dev <
 dev@beam.apache.org> wrote:

> Congratulations Yi!
>
> On Wed, Nov 9, 2022 at 1:34 PM Ahmed Abualsaud via dev <
> dev@beam.apache.org> wrote:
>
>> Congrats Yi!
>>
>> On Wed, Nov 9, 2022 at 1:33 PM Sachin Agarwal via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Congratulations Yi!
>>>
>>> On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles 
>>> wrote:
>>>
 Hi all,

 Please join me and the rest of the Beam PMC in welcoming a new
 committer: Yi Hu (y...@apache.org)

 Yi started contributing to Beam in early 2022. Yi's contributions
 are very diverse! I/Os, performance tests, Jenkins, support for Schema
 logical types. Not only code but a very large amount of code review. 
 Yi is
 also noted for picking up smaller issues that normally would be left 
 on the
 backburner and filing issues that he finds rather than ignoring them.

 Considering their contributions to the project over this timeframe,
 the Beam PMC trusts Yi with the responsibilities of a Beam committer. 
 [1]

 Thank you Yi! And we are looking to see more of your contributions!

 Kenn, on behalf of the Apache Beam PMC

 [1]

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

>>>

Re: [CFP] In-person Beam meetups

[Danielle Syse via dev]

Hi everyone,

I hope you're all having a great start to your week! I want to remind
everyone to join us for our few remaining in-person meetups of the year.
Come network and discuss all things data processing over food and drinks!
Please remember if you share this message to your social channels, you will
automatically be entered into our raffle! Please see the following details
within the Meetup sign-up link.

   - If you're in NYC tonight, please join us at 6PM to hear from
   tech-leaders Daniel Collins, Google Software Engineer, alongside Karen Chin
   and Thomas Jimenez from Wix. Topics will range from Scaling with Data
   Streams to lessons from reimplementing a streaming source. RSVP here:
   https://www.meetup.com/aittg-nyc/events/289399458/
   - Are you located in Bengaluru? Join us Thursday, November 10th, to hear
   from Joinal Ahmed, AI Consultant at Google, as he discusses how to schedule
   and run large-scale ML batch predictions effectively. RSVP here:
   https://www.meetup.com/bangalore-ai-tech-talks/events/288963302/


We can't wait to meet you!

Thanks,

Danielle Syse

On Tue, Nov 8, 2022 at 4:30 PM Aizhamal Nurmamat kyzy 
wrote:

> Hi all,
>
> In person Beam meetup is taking place in NYC tomorrow Nov 9. There will be
> some good talks and pizza :)
>
>  RSVP here: https://www.meetup.com/aittg-nyc/events/289399458/
>
> On Tue, Oct 25, 2022 at 1:56 PM Aizhamal Nurmamat kyzy <
> aizha...@apache.org> wrote:
>
>> Hi all,
>>
>> In-person Beam meetup is taking place in the Bay Area on Nov 2. RSVP
>> here: https://www.meetup.com/aittg-sfsv/events/288939880/
>>
>> We will share the details on NYC and Bangalore meetups soon!
>>
>>
>> On Tue, Oct 11, 2022 at 10:24 AM Aizhamal Nurmamat kyzy <
>> aizha...@apache.org> wrote:
>>
>>> Hey Beam community,
>>>
>>> We are organizing a few in-person community meetups for Apache Beam and
>>> opening up calls for proposals. Please send me directly the topics / ideas
>>> you'd like to present at the following dates and locations:
>>>
>>> November 2, Santa Clara, CA
>>> November 10, NYC
>>> November 12, Bangalore, India
>>>
>>> The typical agenda will look as follows:
>>> 5:30pm~6pm: check in and food
>>> 6:00pm~8pm: 2~3 tech talks
>>> 8pm~8:30pm: mingle and close
>>>
>>> Thanks!
>>>
>>

Re: [ANNOUNCE] New committer: Yi Hu

[Byron Ellis via dev]

Congratulations!

On Wed, Nov 9, 2022 at 11:00 AM Pablo Estrada via dev 
wrote:

> +1 thanks Yi : D
>
> On Wed, Nov 9, 2022 at 10:47 AM Danny McCormick via dev <
> dev@beam.apache.org> wrote:
>
>> Congrats Yi! I've really appreciated the ways you've consistently taken
>> responsibility for improving our team's infra and working through sharp
>> edges in the codebase that others have ignored. This is definitely well
>> deserved!
>>
>> Thanks,
>> Danny
>>
>> On Wed, Nov 9, 2022 at 1:37 PM Anand Inguva via dev 
>> wrote:
>>
>>> Congratulations Yi!
>>>
>>> On Wed, Nov 9, 2022 at 1:35 PM Ritesh Ghorse via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Congratulations Yi!

 On Wed, Nov 9, 2022 at 1:34 PM Ahmed Abualsaud via dev <
 dev@beam.apache.org> wrote:

> Congrats Yi!
>
> On Wed, Nov 9, 2022 at 1:33 PM Sachin Agarwal via dev <
> dev@beam.apache.org> wrote:
>
>> Congratulations Yi!
>>
>> On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles 
>> wrote:
>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new
>>> committer: Yi Hu (y...@apache.org)
>>>
>>> Yi started contributing to Beam in early 2022. Yi's contributions
>>> are very diverse! I/Os, performance tests, Jenkins, support for Schema
>>> logical types. Not only code but a very large amount of code review. Yi 
>>> is
>>> also noted for picking up smaller issues that normally would be left on 
>>> the
>>> backburner and filing issues that he finds rather than ignoring them.
>>>
>>> Considering their contributions to the project over this timeframe,
>>> the Beam PMC trusts Yi with the responsibilities of a Beam committer. 
>>> [1]
>>>
>>> Thank you Yi! And we are looking to see more of your contributions!
>>>
>>> Kenn, on behalf of the Apache Beam PMC
>>>
>>> [1]
>>>
>>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>
>>

Re: [ANNOUNCE] New committer: Yi Hu

[Pablo Estrada via dev]

+1 thanks Yi : D

On Wed, Nov 9, 2022 at 10:47 AM Danny McCormick via dev 
wrote:

> Congrats Yi! I've really appreciated the ways you've consistently taken
> responsibility for improving our team's infra and working through sharp
> edges in the codebase that others have ignored. This is definitely well
> deserved!
>
> Thanks,
> Danny
>
> On Wed, Nov 9, 2022 at 1:37 PM Anand Inguva via dev 
> wrote:
>
>> Congratulations Yi!
>>
>> On Wed, Nov 9, 2022 at 1:35 PM Ritesh Ghorse via dev 
>> wrote:
>>
>>> Congratulations Yi!
>>>
>>> On Wed, Nov 9, 2022 at 1:34 PM Ahmed Abualsaud via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Congrats Yi!

 On Wed, Nov 9, 2022 at 1:33 PM Sachin Agarwal via dev <
 dev@beam.apache.org> wrote:

> Congratulations Yi!
>
> On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles 
> wrote:
>
>> Hi all,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new
>> committer: Yi Hu (y...@apache.org)
>>
>> Yi started contributing to Beam in early 2022. Yi's contributions are
>> very diverse! I/Os, performance tests, Jenkins, support for Schema 
>> logical
>> types. Not only code but a very large amount of code review. Yi is also
>> noted for picking up smaller issues that normally would be left on the
>> backburner and filing issues that he finds rather than ignoring them.
>>
>> Considering their contributions to the project over this timeframe,
>> the Beam PMC trusts Yi with the responsibilities of a Beam committer. [1]
>>
>> Thank you Yi! And we are looking to see more of your contributions!
>>
>> Kenn, on behalf of the Apache Beam PMC
>>
>> [1]
>>
>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>
>

Updated invitation:  Apache Beam Community Meetup: Stateful Feature Backfill @ Fri Nov 18, 2022 11:30am - 12:30pm (CST) (dev@beam.apache.org)

[hello]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20221118T173000Z
DTEND:20221118T183000Z
DTSTAMP:20221109T053247Z
ORGANIZER;CN=Clowder Events:mailto:c_m8k910vjcu6b4b7udo0kngo4d4@group.calen
 dar.google.com
UID:64v3f8f2qiaq4cmlnoa0nqj...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=dev@beam.apache.org;X-NUM-GUESTS=0:mailto:dev@beam.apache.org
X-MICROSOFT-CDO-OWNERAPPTID:-1038132639
CREATED:20221109T045819Z
DESCRIPTION:Stateful feature backfill in Apache BeamAdd this event to your calendar \; https://www.cro
 wdcast.io/e/apache-beam-community-2" id="ow1169" __is_owner="true">Regis
 ter here!In this session\, Ratul Ghosh and Harish
  Nagu Sana will explain how backfill or state bootstrapping is an essential
  capability for streaming applications where data retention for the source 
 is limited to only a few days.This capability will enable Data Scien
 tists\, MLEs\, and Data Engineers to replay the feature-extraction streamin
 g pipeline from archive. Some of the key use cases can be state-bootstrappi
 ng or iterating the featurization logic to fine-tune the ML model training 
 and inference\, etc.The key capability of the Apache Beam-based capa
 bility is transferring the internal state from backfill (batch) to stream.<
 /p>If you want to learn more about this event check out the full agenda
LAST-MODIFIED:20221109T053246Z
LOCATION:https://www.crowdcast.io/e/apache-beam-community-2
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY: Apache Beam Community Meetup: Stateful Feature Backfill
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H10M0S
END:VALARM
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics

Re: [ANNOUNCE] New committer: Yi Hu

[Danny McCormick via dev]

Congrats Yi! I've really appreciated the ways you've consistently taken
responsibility for improving our team's infra and working through sharp
edges in the codebase that others have ignored. This is definitely well
deserved!

Thanks,
Danny

On Wed, Nov 9, 2022 at 1:37 PM Anand Inguva via dev 
wrote:

> Congratulations Yi!
>
> On Wed, Nov 9, 2022 at 1:35 PM Ritesh Ghorse via dev 
> wrote:
>
>> Congratulations Yi!
>>
>> On Wed, Nov 9, 2022 at 1:34 PM Ahmed Abualsaud via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Congrats Yi!
>>>
>>> On Wed, Nov 9, 2022 at 1:33 PM Sachin Agarwal via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Congratulations Yi!

 On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles 
 wrote:

> Hi all,
>
> Please join me and the rest of the Beam PMC in welcoming a new
> committer: Yi Hu (y...@apache.org)
>
> Yi started contributing to Beam in early 2022. Yi's contributions are
> very diverse! I/Os, performance tests, Jenkins, support for Schema logical
> types. Not only code but a very large amount of code review. Yi is also
> noted for picking up smaller issues that normally would be left on the
> backburner and filing issues that he finds rather than ignoring them.
>
> Considering their contributions to the project over this timeframe,
> the Beam PMC trusts Yi with the responsibilities of a Beam committer. [1]
>
> Thank you Yi! And we are looking to see more of your contributions!
>
> Kenn, on behalf of the Apache Beam PMC
>
> [1]
>
> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>

Re: [Python][Bikeshed] typehint vs. type-hint vs. "type hint"

[Robert Burke]

+1 to standardizing on "type hint"

I learned that there's a rule in English that defines when one would have a
space in a compound word or not. If removing one of the components would
change the meaning of the others, the space should be removed.

Eg. By removing "type", it's still a hint, so "type hint" is appropriate.

This rule is why the Apple products are "MacBooks" or "AirPods" rather than
"Mac Book" and "Air Pods". Without the Mac, the laptop isn't a Book.
Without the Air, it's not a "pod".



On Wed, Nov 9, 2022, 10:35 AM Kenneth Knowles  wrote:

> +1 to "type hint" for referring to hinting that something has a particular
> type, and "type" for referring to a... type.
>
> On Mon, Nov 7, 2022 at 7:27 AM Jack McCluskey via dev 
> wrote:
>
>> I'm in agreement that how we refer to type hints in documentation should
>> be standardized across the board. It's a good practice for both style and
>> clarity. Seems like it wouldn't be too hard to update our docstrings
>> either, based on a quick search of the repo.
>>
>> On Mon, Nov 7, 2022 at 9:00 AM Brian Hulette via dev 
>> wrote:
>>
>>> Hi everyone,
>>>
>>> In a recent code review we noticed that we are not consistent when
>>> describing python type hints in documentation. Depending on who wrote the
>>> patch, we switch between typehint, type-hint, and "type hint" [1].
>>>
>>> I think we should standardize on "type hint" as this is what Guido used
>>> in PEP 484 [2]. Please comment on the issue in the next few days if you
>>> disagree with this approach.
>>>
>>> Note this is orthogonal to how we refer to type hints in _code_, in our
>>> public APIs. In general we use "type" in that context (e.g.
>>> `with_input_types`), and there doesn't seem to be a consistency issue.
>>>
>>> [1] https://github.com/apache/beam/issues/23950
>>> [2] https://peps.python.org/pep-0484/
>>>
>>

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

[Chamikara Jayalath via dev]

Ack. There's another potential cherry-pick here:
https://github.com/apache/beam/pull/24041

This should not prevent validation against RC1 for any other potential
regressions.

I'll build a RC2 when cherry-picks are in.

Thanks,
Cham

On Wed, Nov 9, 2022 at 9:30 AM Ritesh Ghorse via dev 
wrote:

> The Dataframe wrapper in Go SDK is failing because of
> https://github.com/apache/beam/issues/24065. I have a PR here
>  to unblock the release. The
> current PR allows Dataframe wrapper to work as expected but proper fix
> should be added while merging RunInference wrapper.
>
> Thanks,
> Ritesh
>
>
> On Wed, Nov 9, 2022 at 8:40 AM Alexey Romanenko 
> wrote:
>
>> +1 (binding)
>>
>> Tested with  https://github.com/Talend/beam-samples/
>> (Java SDK v8 & v11, Spark 3 runner).
>>
>> ---
>> Alexey
>>
>> On 9 Nov 2022, at 01:38, Chamikara Jayalath via dev 
>> wrote:
>>
>> Hi everyone,
>> Please review and vote on the release candidate #1 for the version
>> 2.43.0, as follows:
>> [ ] +1, Approve the release
>> [ ] -1, Do not approve the release (please provide specific comments)
>>
>>
>> Reviewers are encouraged to test their own use cases with the release
>> candidate, and vote +1 if
>> no issues are found.
>>
>> The complete staging area is available for your review, which includes:
>> * GitHub Release notes [1],
>> * the official Apache source release to be deployed to dist.apache.org
>> [2], which is signed with the key with fingerprint
>> 40C61FBE1761E5DB652A1A780CCD5EB2A718A56E [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "v2.43.0-RC1" [5],
>> * website pull request listing the release [6], the blog post [6], and
>> publishing the API reference manual [7].
>> * Java artifacts were built with Gradle 7.5.1 and openjdk version
>> 1.8.0_181-google-v7.
>> * Python artifacts are deployed along with the source release to the
>> dist.apache.org [2] and PyPI[8].
>> * Go artifacts and documentation are available at pkg.go.dev [9]
>> * Validation sheet with a tab for 2.43.0 release to help with validation
>> [10].
>> * Docker images published to Docker Hub [11].
>>
>> The vote will be open for at least 72 hours. It is adopted by majority
>> approval, with at least 3 PMC affirmative votes.
>>
>> For guidelines on how to try the release in your projects, check out our
>> blog post at https://beam.apache.org/blog/validate-beam-release/.
>>
>> Thanks,
>> Cham
>>
>> [1] https://github.com/apache/beam/milestone/5
>> [2] https://dist.apache.org/repos/dist/dev/beam/2.43.0/
>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1287/
>> [5] https://github.com/apache/beam/tree/v2.43.0-RC1
>> [6] https://github.com/apache/beam/pull/24044
>> [7] https://github.com/apache/beam-site/pull/635
>> [8] https://pypi.org/project/apache-beam/2.43.0rc1/
>> [9]
>> https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.43.0-RC1/go/pkg/beam
>> [10]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1310009119
>> [11] https://hub.docker.com/search?q=apache%2Fbeam=image
>>
>>
>>

Re: [ANNOUNCE] New committer: Yi Hu

[Anand Inguva via dev]

Congratulations Yi!

On Wed, Nov 9, 2022 at 1:35 PM Ritesh Ghorse via dev 
wrote:

> Congratulations Yi!
>
> On Wed, Nov 9, 2022 at 1:34 PM Ahmed Abualsaud via dev <
> dev@beam.apache.org> wrote:
>
>> Congrats Yi!
>>
>> On Wed, Nov 9, 2022 at 1:33 PM Sachin Agarwal via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Congratulations Yi!
>>>
>>> On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles  wrote:
>>>
 Hi all,

 Please join me and the rest of the Beam PMC in welcoming a new
 committer: Yi Hu (y...@apache.org)

 Yi started contributing to Beam in early 2022. Yi's contributions are
 very diverse! I/Os, performance tests, Jenkins, support for Schema logical
 types. Not only code but a very large amount of code review. Yi is also
 noted for picking up smaller issues that normally would be left on the
 backburner and filing issues that he finds rather than ignoring them.

 Considering their contributions to the project over this timeframe, the
 Beam PMC trusts Yi with the responsibilities of a Beam committer. [1]

 Thank you Yi! And we are looking to see more of your contributions!

 Kenn, on behalf of the Apache Beam PMC

 [1]

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

>>>

Re: [ANNOUNCE] New committer: Yi Hu

[Ritesh Ghorse via dev]

Congratulations Yi!

On Wed, Nov 9, 2022 at 1:34 PM Ahmed Abualsaud via dev 
wrote:

> Congrats Yi!
>
> On Wed, Nov 9, 2022 at 1:33 PM Sachin Agarwal via dev 
> wrote:
>
>> Congratulations Yi!
>>
>> On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles  wrote:
>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new
>>> committer: Yi Hu (y...@apache.org)
>>>
>>> Yi started contributing to Beam in early 2022. Yi's contributions are
>>> very diverse! I/Os, performance tests, Jenkins, support for Schema logical
>>> types. Not only code but a very large amount of code review. Yi is also
>>> noted for picking up smaller issues that normally would be left on the
>>> backburner and filing issues that he finds rather than ignoring them.
>>>
>>> Considering their contributions to the project over this timeframe, the
>>> Beam PMC trusts Yi with the responsibilities of a Beam committer. [1]
>>>
>>> Thank you Yi! And we are looking to see more of your contributions!
>>>
>>> Kenn, on behalf of the Apache Beam PMC
>>>
>>> [1]
>>>
>>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>
>>

Re: [Python][Bikeshed] typehint vs. type-hint vs. "type hint"

[Kenneth Knowles]

+1 to "type hint" for referring to hinting that something has a particular
type, and "type" for referring to a... type.

On Mon, Nov 7, 2022 at 7:27 AM Jack McCluskey via dev 
wrote:

> I'm in agreement that how we refer to type hints in documentation should
> be standardized across the board. It's a good practice for both style and
> clarity. Seems like it wouldn't be too hard to update our docstrings
> either, based on a quick search of the repo.
>
> On Mon, Nov 7, 2022 at 9:00 AM Brian Hulette via dev 
> wrote:
>
>> Hi everyone,
>>
>> In a recent code review we noticed that we are not consistent when
>> describing python type hints in documentation. Depending on who wrote the
>> patch, we switch between typehint, type-hint, and "type hint" [1].
>>
>> I think we should standardize on "type hint" as this is what Guido used
>> in PEP 484 [2]. Please comment on the issue in the next few days if you
>> disagree with this approach.
>>
>> Note this is orthogonal to how we refer to type hints in _code_, in our
>> public APIs. In general we use "type" in that context (e.g.
>> `with_input_types`), and there doesn't seem to be a consistency issue.
>>
>> [1] https://github.com/apache/beam/issues/23950
>> [2] https://peps.python.org/pep-0484/
>>
>

Re: [ANNOUNCE] New committer: Yi Hu

[Ahmed Abualsaud via dev]

Congrats Yi!

On Wed, Nov 9, 2022 at 1:33 PM Sachin Agarwal via dev 
wrote:

> Congratulations Yi!
>
> On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles  wrote:
>
>> Hi all,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new
>> committer: Yi Hu (y...@apache.org)
>>
>> Yi started contributing to Beam in early 2022. Yi's contributions are
>> very diverse! I/Os, performance tests, Jenkins, support for Schema logical
>> types. Not only code but a very large amount of code review. Yi is also
>> noted for picking up smaller issues that normally would be left on the
>> backburner and filing issues that he finds rather than ignoring them.
>>
>> Considering their contributions to the project over this timeframe, the
>> Beam PMC trusts Yi with the responsibilities of a Beam committer. [1]
>>
>> Thank you Yi! And we are looking to see more of your contributions!
>>
>> Kenn, on behalf of the Apache Beam PMC
>>
>> [1]
>>
>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>
>

Re: [ANNOUNCE] New committer: Yi Hu

[Sachin Agarwal via dev]

Congratulations Yi!

On Wed, Nov 9, 2022 at 10:32 AM Kenneth Knowles  wrote:

> Hi all,
>
> Please join me and the rest of the Beam PMC in welcoming a new
> committer: Yi Hu (y...@apache.org)
>
> Yi started contributing to Beam in early 2022. Yi's contributions are very
> diverse! I/Os, performance tests, Jenkins, support for Schema logical
> types. Not only code but a very large amount of code review. Yi is also
> noted for picking up smaller issues that normally would be left on the
> backburner and filing issues that he finds rather than ignoring them.
>
> Considering their contributions to the project over this timeframe, the
> Beam PMC trusts Yi with the responsibilities of a Beam committer. [1]
>
> Thank you Yi! And we are looking to see more of your contributions!
>
> Kenn, on behalf of the Apache Beam PMC
>
> [1]
>
> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>

[ANNOUNCE] New committer: Yi Hu

[Kenneth Knowles]

Hi all,

Please join me and the rest of the Beam PMC in welcoming a new
committer: Yi Hu (y...@apache.org)

Yi started contributing to Beam in early 2022. Yi's contributions are very
diverse! I/Os, performance tests, Jenkins, support for Schema logical
types. Not only code but a very large amount of code review. Yi is also
noted for picking up smaller issues that normally would be left on the
backburner and filing issues that he finds rather than ignoring them.

Considering their contributions to the project over this timeframe, the
Beam PMC trusts Yi with the responsibilities of a Beam committer. [1]

Thank you Yi! And we are looking to see more of your contributions!

Kenn, on behalf of the Apache Beam PMC

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

Re: [DISCUSS] Avro dependency update, design doc

[Austin Bennett]

Being tied to a specific version of a dependency, and esp. one that is
not-[actually-long-term]critical, sounds like a problem.  It doesn't seem
like Avro needs to be in core.  I am in favor of about any path someone
wants to address towards removing that from core [ *#2 in the design doc
seems reasonable* ].

Naturally, having ways to more easily change versions [esp. to remediate
CVEs, but for any specific reason ], seems very valuable.

It reads as a significant problem; I wouldn't take issue with a breaking [
compile time ] change, if that got things addressed and somewhat
straightforwardly - *I am concerned of what could go wrong for users in the
in-between/transition state while more slowly transitioning avro to
extension.*

On Wed, Nov 9, 2022 at 5:43 AM Alexey Romanenko 
wrote:

> Any thoughts on this? For now, we'd need to decide which path finally to
> take to move forward.
>
> Thanks in advance!
>
> —
> Alexey
>
> On 4 Nov 2022, at 16:44, Alexey Romanenko 
> wrote:
>
> Hi all,
>
> Following-up an Avro dependency update discussion [1] that showed a lot of
> uncertainties to move forward, Moritz and I decided to create a design
> document [2] with potential options, that we believe, can be considered and
> used further. Unfortunately, all solutions lead to breaking changes in some
> way, though, for some of them the negative effect can be reduced by
> preparing users for this in advance and make this transition smoother.
>
> Please, take a look on this doc and leave your comments and opinions -
> your feedback is very welcomed!
>
> [1] https://lists.apache.org/thread/mz8hvz8dwhd0tzmv2lyobhlz7gtg4gq7
> [2]
> https://docs.google.com/document/d/1tKIyTk_-HhkmVuJsxvWP5eTELESpCBe_Vmb1nJ3Ia34/edit?usp=sharing
>
> —
> Alexey
>
>
>

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

[Ritesh Ghorse via dev]

The Dataframe wrapper in Go SDK is failing because of
https://github.com/apache/beam/issues/24065. I have a PR here
 to unblock the release. The
current PR allows Dataframe wrapper to work as expected but proper fix
should be added while merging RunInference wrapper.

Thanks,
Ritesh


On Wed, Nov 9, 2022 at 8:40 AM Alexey Romanenko 
wrote:

> +1 (binding)
>
> Tested with  https://github.com/Talend/beam-samples/
> (Java SDK v8 & v11, Spark 3 runner).
>
> ---
> Alexey
>
> On 9 Nov 2022, at 01:38, Chamikara Jayalath via dev 
> wrote:
>
> Hi everyone,
> Please review and vote on the release candidate #1 for the version 2.43.0,
> as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
>
> Reviewers are encouraged to test their own use cases with the release
> candidate, and vote +1 if
> no issues are found.
>
> The complete staging area is available for your review, which includes:
> * GitHub Release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
> [2], which is signed with the key with fingerprint
> 40C61FBE1761E5DB652A1A780CCD5EB2A718A56E [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.43.0-RC1" [5],
> * website pull request listing the release [6], the blog post [6], and
> publishing the API reference manual [7].
> * Java artifacts were built with Gradle 7.5.1 and openjdk version
> 1.8.0_181-google-v7.
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2] and PyPI[8].
> * Go artifacts and documentation are available at pkg.go.dev [9]
> * Validation sheet with a tab for 2.43.0 release to help with validation
> [10].
> * Docker images published to Docker Hub [11].
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> For guidelines on how to try the release in your projects, check out our
> blog post at https://beam.apache.org/blog/validate-beam-release/.
>
> Thanks,
> Cham
>
> [1] https://github.com/apache/beam/milestone/5
> [2] https://dist.apache.org/repos/dist/dev/beam/2.43.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1287/
> [5] https://github.com/apache/beam/tree/v2.43.0-RC1
> [6] https://github.com/apache/beam/pull/24044
> [7] https://github.com/apache/beam-site/pull/635
> [8] https://pypi.org/project/apache-beam/2.43.0rc1/
> [9]
> https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.43.0-RC1/go/pkg/beam
> [10]
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1310009119
> [11] https://hub.docker.com/search?q=apache%2Fbeam=image
>
>
>

Re: [DISCUSS] Avro dependency update, design doc

[Alexey Romanenko]

Any thoughts on this? For now, we'd need to decide which path finally to take 
to move forward.

Thanks in advance!

—
Alexey

> On 4 Nov 2022, at 16:44, Alexey Romanenko  wrote:
> 
> Hi all,
> 
> Following-up an Avro dependency update discussion [1] that showed a lot of 
> uncertainties to move forward, Moritz and I decided to create a design 
> document [2] with potential options, that we believe, can be considered and 
> used further. Unfortunately, all solutions lead to breaking changes in some 
> way, though, for some of them the negative effect can be reduced by preparing 
> users for this in advance and make this transition smoother.
> 
> Please, take a look on this doc and leave your comments and opinions - your 
> feedback is very welcomed!
> 
> [1] https://lists.apache.org/thread/mz8hvz8dwhd0tzmv2lyobhlz7gtg4gq7 
> [2] 
> https://docs.google.com/document/d/1tKIyTk_-HhkmVuJsxvWP5eTELESpCBe_Vmb1nJ3Ia34/edit?usp=sharing
>  
> 
> 
> —
> Alexey

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

[Alexey Romanenko]

+1 (binding)

Tested with  https://github.com/Talend/beam-samples/ 
 
(Java SDK v8 & v11, Spark 3 runner).

---
Alexey

> On 9 Nov 2022, at 01:38, Chamikara Jayalath via dev  
> wrote:
> 
> Hi everyone,
> Please review and vote on the release candidate #1 for the version 2.43.0, as 
> follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
> 
> 
> Reviewers are encouraged to test their own use cases with the release 
> candidate, and vote +1 if
> no issues are found.
> 
> The complete staging area is available for your review, which includes:
> * GitHub Release notes [1],
> * the official Apache source release to be deployed to dist.apache.org 
>  [2], which is signed with the key with fingerprint 
> 40C61FBE1761E5DB652A1A780CCD5EB2A718A56E [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.43.0-RC1" [5],
> * website pull request listing the release [6], the blog post [6], and 
> publishing the API reference manual [7].
> * Java artifacts were built with Gradle 7.5.1 and openjdk version 
> 1.8.0_181-google-v7.
> * Python artifacts are deployed along with the source release to the 
> dist.apache.org  [2] and PyPI[8].
> * Go artifacts and documentation are available at pkg.go.dev 
>  [9]
> * Validation sheet with a tab for 2.43.0 release to help with validation [10].
> * Docker images published to Docker Hub [11].
> 
> The vote will be open for at least 72 hours. It is adopted by majority 
> approval, with at least 3 PMC affirmative votes.
> 
> For guidelines on how to try the release in your projects, check out our blog 
> post at https://beam.apache.org/blog/validate-beam-release/ 
> .
> 
> Thanks,
> Cham
> 
> [1] https://github.com/apache/beam/milestone/5 
> 
> [2] https://dist.apache.org/repos/dist/dev/beam/2.43.0/ 
> 
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS 
> 
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1287/ 
> 
> [5] https://github.com/apache/beam/tree/v2.43.0-RC1 
> 
> [6] https://github.com/apache/beam/pull/24044 
> 
> [7] https://github.com/apache/beam-site/pull/635 
> 
> [8] https://pypi.org/project/apache-beam/2.43.0rc1/ 
> 
> [9] https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.43.0-RC1/go/pkg/beam 
> 
> [10] 
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1310009119
>  
> 
> [11] https://hub.docker.com/search?q=apache%2Fbeam=image 
> 

Beam High Priority Issue Report (65)

[beamactions]

This is your daily summary of Beam's current high priority issues that may need 
attention.

See https://beam.apache.org/contribute/issue-priorities for the meaning and 
expectations around issue priorities.

Unassigned P1 Issues:

https://github.com/apache/beam/issues/24021 [Bug]: SparkReceriverIO and KafkaIO 
performance tests failing due to unschedulable pods on k8s
https://github.com/apache/beam/issues/24016 Failure in test: 
"beam_PerformanceTests_Kafka_IO" - timed out waiting for the condition on 
jobs/kafka-config
https://github.com/apache/beam/issues/23982 [Bug]: Could not find a version 
that matches protobuf
https://github.com/apache/beam/issues/23974 [Bug]: The top tesult for "Beam 
godocs" in Google points to an old Godocs page of Beam
https://github.com/apache/beam/issues/23944  beam_PreCommit_Python_Cron 
regularily failing - test_pardo_large_input flaky
https://github.com/apache/beam/issues/23940 beam_PostCommit_Py_ValCont failing
https://github.com/apache/beam/issues/23815 [Bug]: Neo4j tests failing
https://github.com/apache/beam/issues/23745 [Bug]: Samza 
AsyncDoFnRunnerTest.testSimplePipeline is flaky
https://github.com/apache/beam/issues/23709 [Flake]: Spark batch flakes in 
ParDoLifecycleTest.testTeardownCalledAfterExceptionInProcessElement and 
ParDoLifecycleTest.testTeardownCalledAfterExceptionInStartBundle
https://github.com/apache/beam/issues/22969 Discrepancy in behavior of 
`DoFn.process()` when `yield` is combined with `return` statement, or vice versa
https://github.com/apache/beam/issues/22913 [Bug]: 
beam_PostCommit_Java_ValidatesRunner_Flink is flakes in 
org.apache.beam.sdk.transforms.GroupByKeyTest$BasicTests.testAfterProcessingTimeContinuationTriggerUsingState
https://github.com/apache/beam/issues/22321 
PortableRunnerTestWithExternalEnv.test_pardo_large_input is regularly failing 
on jenkins
https://github.com/apache/beam/issues/21713 404s in BigQueryIO don't get output 
to Failed Inserts PCollection
https://github.com/apache/beam/issues/21561 
ExternalPythonTransformTest.trivialPythonTransform flaky
https://github.com/apache/beam/issues/21469 beam_PostCommit_XVR_Flink flaky: 
Connection refused
https://github.com/apache/beam/issues/21462 Flake in 
org.apache.beam.sdk.io.mqtt.MqttIOTest.testReadObject: Address already in use
https://github.com/apache/beam/issues/21261 
org.apache.beam.runners.dataflow.worker.fn.logging.BeamFnLoggingServiceTest.testMultipleClientsFailingIsHandledGracefullyByServer
 is flaky
https://github.com/apache/beam/issues/21260 Python DirectRunner does not emit 
data at GC time
https://github.com/apache/beam/issues/21123 Multiple jobs running on Flink 
session cluster reuse the persistent Python environment.
https://github.com/apache/beam/issues/21113 
testTwoTimersSettingEachOtherWithCreateAsInputBounded flaky
https://github.com/apache/beam/issues/20976 
apache_beam.runners.portability.flink_runner_test.FlinkRunnerTestOptimized.test_flink_metrics
 is flaky
https://github.com/apache/beam/issues/20975 
org.apache.beam.runners.flink.ReadSourcePortableTest.testExecution[streaming: 
false] is flaky
https://github.com/apache/beam/issues/20974 Python GHA PreCommits flake with 
grpc.FutureTimeoutError on SDK harness startup
https://github.com/apache/beam/issues/20689 Kafka commitOffsetsInFinalize OOM 
on Flink
https://github.com/apache/beam/issues/20108 Python direct runner doesn't emit 
empty pane when it should
https://github.com/apache/beam/issues/19814 Flink streaming flakes in 
ParDoLifecycleTest.testTeardownCalledAfterExceptionInStartBundleStateful and 
ParDoLifecycleTest.testTeardownCalledAfterExceptionInProcessElementStateful
https://github.com/apache/beam/issues/19734 
WatchTest.testMultiplePollsWithManyResults flake: Outputs must be in timestamp 
order (sickbayed)
https://github.com/apache/beam/issues/19241 Python Dataflow integration tests 
should export the pipeline Job ID and console output to Jenkins Test Result 
section


P1 Issues with no update in the last week:

https://github.com/apache/beam/issues/23906 [Bug]: Dataflow jpms tests fail on 
the 2.43.0 release branch
https://github.com/apache/beam/issues/23875 [Bug]: beam.Row.__eq__ returns true 
for unequal rows
https://github.com/apache/beam/issues/23855 [FLAKY-WORKFLOW] [10535797]: THIS 
IS A TEST, PLEASE IGNORE #1
https://github.com/apache/beam/issues/23627 [Bug]: Website precommit flaky
https://github.com/apache/beam/issues/23525 [Bug]: Default PubsubMessage coder 
will drop message id and orderingKey
https://github.com/apache/beam/issues/23489 [Bug]: add DebeziumIO to the 
connectors page
https://github.com/apache/beam/issues/23306 [Bug]: BigQueryBatchFileLoads in 
python loses data when using WRITE_TRUNCATE
https://github.com/apache/beam/issues/23286 [Bug]: 
beam_PerformanceTests_InfluxDbIO_IT Flaky > 50 % Fail 
https://github.com/apache/beam/issues/22891 [Bug]: 
beam_PostCommit_XVR_PythonUsingJavaDataflow is flaky
https://github.com/apache/beam/issues/22605 [Bug]: Beam Python