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

Those particular errors are often expected in the sink due to the protocol used. If a work item retries before committing (which could happen for many reasons including worker crashes), it will experience those errors. On Fri, Apr 28, 2023 at 12:55 PM Ahmed Abualsaud wrote: > @Danny McCormick @

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

@Danny McCormick @Reuven Lax sorry it's been a while since you looked into this, but do you remember if the fix in #25642 issue is related to the recent "ALREADY_EXISTS: The offset is within stream, expected offset..." errors? On Fri, Mar 10, 2023 at 7

Re: Starter projects for Beam

Hello Svetak, Thanks for the suggestion. I will look into them. Sincerely, Tariq Hasan On Fri, Apr 28, 2023 at 2:21 PM Svetak Sundhar via dev wrote: > Hi Tariq, > > Thanks for your interest! A good starting point are good first issues: > https://github.com/apache/beam/labels/good%20first%20i

Re: Starter projects for Beam

Hi Tariq, Thanks for your interest! A good starting point are good first issues: https://github.com/apache/beam/labels/good%20first%20issue?page=2&q=is%3Aopen+label%3A%22good+first+issue%22 . Feel free to assign an issue to yourself and put up a PR/ask any needed questions when ready. Thanks,

Starter projects for Beam

Hello, I am reaching out as a new entrant into the Apache Beam project. As a developer with a few years of experience, I was looking to grow my passion around software development through open-source contributions. With Apache Beam, I am quite interested in working across multiple areas, includi

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

The move to support and require protobuf v4 in the python SDK has inadvertently broken downstream users who depend on Beam, who have asked if that requirement can be lowered to also allow protobuf v3. Further investigation has determined that the lower bounds of this requirement can be relaxed with

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

+1 (binding) Tested with https://github.com/Talend/beam-samples/ (Java SDK v8/v11/v17, Spark 3.x runner). --- Alexey > On 28 Apr 2023, at 16:06, Jack McCluskey via dev wrote: > > There was a GCP outage that impacted pushing containers to GCR, I expected it > to impact Java containers specif

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

There was a GCP outage that impacted pushing containers to GCR, I expected it to impact Java containers specifically but it looks like it also affected Python containers. I believe the situation is resolved and I can get the containers pushed now, if that continues to be an issue I'll follow up. O

Beam High Priority Issue Report (30)

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/26458 [Bug]: Error instal

Re: Regarding Project proposal review and feedback

Hello Jeff, Thank you for the idea, as it will allow beam users to write sql queries using the Beam SQL API and execute them on the Flink Table API.I will look into it later as my current focus is to implement an integration between Apache Beam and the Flink DataStream API. While the existing Flink

Re: Regarding Project proposal review and feedback

Hello David, First of all thanks for the reply .Now answering your question I would like to state that Yes, I am aware that there is an existing Flink runner based on the DataStream and Operator API in the Beam codebase. However, the runner I propose to develop will differ from the existing one in