Beam High Priority Issue Report (69)

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/23020 [Bug]: Kubernetes s

Re: [PROPOSAL] Preparing for 2.42.0 Release

Thanks for taking this on! Kenn On Wed, Aug 24, 2022 at 3:05 PM Robert Burke wrote: > Hi everyone! > > The next (2.42.0) release branch cut is scheduled for Sept 7th, according > to > the release calendar [1]. > > I would like to volunteer myself to do this release. My plan is to cut > the bran

Re: [ANNOUNCE] Apache Beam 2.41.0 Released

Thanks! On Fri, Aug 26, 2022 at 11:47 AM Byron Ellis via dev wrote: > Thanks Kiley! > > On Fri, Aug 26, 2022 at 9:37 AM Ahmet Altay via dev > wrote: > >> Thank you Kiley! >> >> On Fri, Aug 26, 2022 at 6:38 AM P Singh >> wrote: >> >>> Hi Team, >>> >>> Looking forward to trying and testing the n

Re: Java compatibility checking library

Aha! I found a reference to using japicmp for this purpose even earlier, at our first stable release :-) https://lists.apache.org/thread/8chz1pp3drg8kbv84yfq9mct31ohcvvd I just noticed on dev@flink that there's a proposal to use it there ( https://lists.apache.org/thread/jkk87ls2lc17q6bqz5b1xzh67

Upcoming potentially breaking change to CoGroupByKey

CoGroupByKey returns a dictionary of {KeyType, List[ValueType]} but, as GroupByKey, should return an Iterable. Change: https://github.com/apache/beam/pull/22984 Please look at this doc if you need more details. Feel

Re: Upcoming potentially breaking change to CoGroupByKey

Thank you for already planning to *NOT* have this merged until after this week's 2.42.0 cut. This Release Manager is pleased that the doc says it's intended for 2.43.0. On Tue, Sep 6, 2022, 1:44 PM Ryan Thompson via dev wrote: > CoGroupByKey returns a dictionary of {KeyType, List[ValueType]} bu

Re: Upcoming potentially breaking change to CoGroupByKey

We should send this out to us...@beam.apache.org so that they are aware of this change once commenting in the doc has settled. On Tue, Sep 6, 2022 at 1:59 PM Robert Burke wrote: > Thank you for already planning to *NOT* have this merged until after this > week's 2.42.0 cut. This Release Manager

Re: Upcoming potentially breaking change to CoGroupByKey

There was discussion in the python meeting to try to get this into the new release. The consensus was that putting it in right after the release had the highest chance of catching problems with the least amount of pain. I can send it out to users next week if nother halts the change. On Tue, Sep

Re: Upcoming potentially breaking change to CoGroupByKey

"new release" is an ambiguous descriptor in this email. I'm going to continue to take it as "right after the 2.42.0 cut, to make it into the 2.43.0 as planned". On Tue, Sep 6, 2022 at 2:39 PM Ryan Thompson wrote: > There was discussion in the python meeting to try to get this into the new > rele