Different Beam project launched

https://github.com/slai-labs/get-beam This seems to overlap with our branding/messaging on ML. Kerry

Re: Proposal for pyproject.toml Support in Apache Beam Python

+1 Hi Anand, I appreciate this effort. Managing python dependencies has been a major pain point for me, and I think this approach would help. Kerry On Mon, Aug 28, 2023 at 10:14 AM Anand Inguva via dev wrote: > Hello Beam Dev Team, > > I've compiled a design document >

Re: [ANNOUNCE] New committer: Ahmed Abualsaud

Well done Ahmed! On Fri, Aug 25, 2023 at 9:17 AM Danny McCormick via dev wrote: > Congrats Ahmed! > > On Fri, Aug 25, 2023 at 3:16 AM Jan Lukavský wrote: > >> Congrats Ahmed! >> On 8/25/23 07:56, Anand Inguva via dev wrote: >> >> Congratulations Ahmed :) >> >> On Fri, Aug 25, 2023 at 1:17 AM Da

Re: [PROPOSAL] Design Doc template for PTransforms

Thanks Kenn! I think this would be a great community resource. While we don't want to enforce usage, perhaps we could introduce tooling to check basic compliance and raise a warning. Similar to a linter or test suite. Kerry On Thu, Aug 24, 2023 at 10:25 AM Kenneth Knowles wrote: > Hi all, > > Ba

Re: Beam Website Feedback

Thanks Jonas. Can you please submit a quick PR to update the text? I'm happy to review. Kerry On Wed, Aug 23, 2023, 10:03 PM Jonas Eyob wrote: > Hi on this page: > https://beam.apache.org/documentation/io/built-in/google-bigquery/#storage-api > > > > Under ”Using Storage Read API” there is a par

Re: [RFC] Bootloader Buffered Logging

Much appreciated, reviewing the doc now. On Wed, Aug 16, 2023 at 9:08 PM Valentyn Tymofieiev via dev < dev@beam.apache.org> wrote: > Thanks, Jack! left some comments, looking forward to this work! > > On Wed, Aug 16, 2023 at 10:31 AM Robert Burke wrote: > >> I've added some comments but generall

Re: [Discuss] Get rid of OWNERS files

Thanks Danny! I agree. OWNERS causes unnecessary friction, and doesn't provide value. Kerry On Tue, Aug 8, 2023 at 10:55 AM Danny McCormick via dev wrote: > Hey everyone, I'd like to propose getting rid of OWNERS files from the > Beam repo. Right now, I don't think they are serving a meaningful

Re: Asgarde: Error Handling for Beam?

This looks like an excellent contribution. I can easily understand the motivation, and I think Beam would benefit from a higher level abstraction for error handling. Kerry On Wed, Jun 14, 2023, 6:31 PM Austin Bennett wrote: > Hi Beam Devs, > > @Mazlum

Re: [beam-starter-typescript]: Missing place to create issue

Jack may also be able to help you create an issue. Kerry On Wed, Jun 14, 2023, 1:09 PM XQ Hu via dev wrote: > I believe Robert is the owner for that project. > > On Mon, Jun 12, 2023 at 11:30 PM david-kh...@hotmail.com < > david-kh...@hotmail.com> wrote: > >> Hi Beam community, >> >> >> >> I am

[Proposal] DNS name for Tour of Beam site

Hi all, I would like to update everyone on a small DNS change for the Tour Of Beam, a new Beam interactive learning app we've been working on. We are excited to get it live and share it with the community, and one of the remaining steps for us is to make a DNS record for 'tour.beam.apache.org' and

Re: [ANNOUNCE] New committer: Damon Douglas

Damon, you have done outstanding work to grow and improve Beam and the Beam community. Well done, well deserved! On Mon, Apr 24, 2023 at 4:39 PM XQ Hu via dev wrote: > Congrats Damon!!! > > On Mon, Apr 24, 2023 at 4:34 PM Danny McCormick via dev < > dev@beam.apache.org> wrote: > >> Congrats Damo

Re: [ANNOUNCE] New committer: Anand Inguva

Great work Anand, this is well deserved. On Mon, Apr 24, 2023 at 10:35 AM Yi Hu via dev wrote: > Congrats Anand! > > On Fri, Apr 21, 2023 at 3:54 PM Danielle Syse via dev > wrote: > >> Congratulations! >> >> On Fri, Apr 21, 2023 at 3:53 PM Damon Douglas via dev < >> dev@beam.apache.org> wrote:

Re: [DISCUSS] @Experimental, @Internal, @Stable, etc annotations

+1 to eliminating @Experimental as a Beam level annotation. I think the main point is that if no one pays attention to such annotations, then they are only noise and deliver negative value. Kerry PS- Kenn says " the point about the culture of stagnation came from my recent experiences as code revi

Re: Beam Release DockerHub Group

+1, should there also be an update to remove folks who are not active on the project? Kerry On Mon, Apr 17, 2023 at 11:40 AM Jack McCluskey via dev wrote: > +1 to simplifying the infra side, especially with an aim towards > automating the processes we can. The more we can streamline and simplify

Re: 2.47.0 Release Update and Brief Code Freeze

Thanks for the transparent and quick explanation! Identifying an issue, taking steps to correct it, and documenting what went wrong is exactly how we should address isssues like this. Kerry On Wed, Apr 5, 2023, 4:53 PM Jack McCluskey via dev wrote: > Hey everyone, > > While I was working on cutt

Re: Launch Dataflow Flex Templates from Go

Jack added the Go templates capabilities, he should be able to help you out. On Wed, Feb 15, 2023, 12:37 AM Ashok KS wrote: > Hi Shivam, > > Thanks a lot for your response. I did check the http request. But I wanted > to see if I can use the Google API client Library. > The docs show a Python ex

Re: Exploring existing Beam features to prevent web service API overuse

Thanks Damon, I appreciate the data-driven effort you are making to test different approaches to rate limiting in Beam. On Thu, Feb 9, 2023 at 12:54 AM Damon Douglas wrote: > Hello Everyone, > > The following exploratory study proposal aims to evaluate existing > features of Beam to prevent web

Re: Achievement unlocked: fully triaged

t would automatically mark >>>>> self-assigned self-reported issues as triaged. That is probably a third of >>>>> issues or more. >>>>> >>>>> I believe that automation exists now[1], but it wasn't retroactively >>>>> appli

Re: Gradle Task Configuration Avoidance

Thanks Damon! I really appreciate how clear your emails are here. Instead of my usual feeling of "I don't quite understand, and don't have time to get context" I can read all the context in the mail. This error message had confused me, so I really appreciate the cleanup and explanation. On Fri, De

Re: Achievement unlocked: fully triaged

This is a glorious achievement Kenn! To keep things clean going forward are there any improvements we can make in our issue creation flow? On Fri, Dec 2, 2022, 6:44 PM Kenneth Knowles wrote: > Hi all, > > I've finally done it! I've emptied the label "awaiting triage". Help me > keep it that way!

Re: Open Pull Request to improve documentation

Hi Laksh, I see that you have found a reviewer. In the future, or for anyone else, we have GitHub Actions that should automatically assign a reviewer and guide the review and approval flows. If you wait for a day and don't see a reviewer automatically assigned please email the dev list and we will

Re: [ANNOUNCE] New committer: Yi Hu

Great job Yi! I am happy to see your contributions recognized. On Thu, Nov 10, 2022 at 11:52 AM Yi Hu via dev wrote: > Thank you for the help of you all over the time, and I am glad to > contribute and help with the community. > > Best, > Yi > > On Thu, Nov 10, 2022 at 11:29 AM Alexey Romanenko

Re: [ANNOUNCE] New committer: Ritesh Ghorse

Congratulations Ritesh, I'm happy to see your hard work and community spirit recognized! On Fri, Nov 4, 2022 at 10:16 AM Jack McCluskey via dev wrote: > Congrats Ritesh! > > On Thu, Nov 3, 2022 at 10:12 PM Danny McCormick via dev < > dev@beam.apache.org> wrote: > >> Congrats Ritesh! This is defi

Re: [DISCUSS] Dependency management in Apache Beam Python SDK

Jarek, I really appreciate you sharing your experience and expertise here. I think Beam would benefit from adopting some of these practices. Kerry On Fri, Aug 26, 2022, 7:35 AM Jarek Potiuk wrote: > >> I'm curious Jarek, does Airflow take any dependencies on popular >> libraries like pandas, num

Re: [ANNOUNCE] New committer: John Casey

John, you have made a huge impact on the many, many users of Kafka and other IOs. This is great recognition of your commitment to Beam. Kerry On Fri, Jul 29, 2022 at 4:46 PM Byron Ellis via dev wrote: > Congratulations John! > > On Fri, Jul 29, 2022 at 1:09 PM Danny McCormick via dev < > dev@bea

Re: [RFC] State & Timers API Design for Go SDK

I think this a perfect example of a clear design doc. Great, deeply detailed alternatives considered and why they were rejected. This makes review easy, and lets us follow your thought process. I think this is a good implementation, and I support the chosen approach. Kerry On Thu, Jul 28, 2022 at