Beam High Priority Issue Report (39)

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/27892 [Bug]: ignoreUnknow

Re: [PROPOSAL] Preparing for 2.50.0 Release

Thanks for driving this Robert! It seems the two PRs specified have been merged. A little new to Beam, do we have an expected release date for the 2.50 release? Best, Hong On Thu, Aug 10, 2023 at 3:08 AM Robert Burke wrote: > I'm in the process of producing the Cut branch, but due to various d

Re: [PROPOSAL] Preparing for 2.50.0 Release

The release branch was cut. Before yhe weekend, I was working on getting the non-portable Dataflow Java worker built and available before producing the RC1. The actual building bit doesn't take that long, but there's a bunch of additional validation that goes along with it. The current target date

Re: Beam IO Connector

I believe Devon Peticolas wrote a similar tool to create an IO that wrote to configurable sinks that might fit your use case On Sat, Aug 12, 2023 at 12:18 PM Bruno Volpato via dev wrote: > Hi Jeremy, > > Apparently you are trying to use Beam's DirectRunner >

Re: [PROPOSAL] Preparing for 2.50.0 Release

I see, thanks for clarifying, Robert!Is there anything I can help with validation? Is there a wiki page with the expected validations I can help with?BestHongOn 14 Aug 2023, at 14:34, Robert Burke wrote:The release branch was cut. Before yhe weekend, I was working on getting the non-portable Data

Re: Propose to add the new security section to the Beam releases

Great idea. On Fri, Aug 11, 2023 at 2:18 PM XQ Hu via dev wrote: > Hi All, > > We are proposing to explicitly add the security fixes to the Beam release > notes. https://github.com/apache/beam/pull/27976 modified the template in > CHANGES.md > by adding this new section. > > Please let us know

Re: Seeking Assistance to Resolve Issues/bug with Flink Runner on Kubernetes

There is a slack channel linked from https://beam.apache.org/community/contact-us/ it is #beam on the-asf.slack.com (you find this via beam.apache.org -> Community -> Contact Us) It sounds like an issue with running a multi-language pipeline on the portable flink runner. (something which I am not

Re: Beam IO Connector

Thanks. Is there a github link to Devon's code? On Mon, Aug 14, 2023 at 8:49 AM John Casey wrote: > I believe Devon Peticolas wrote a similar tool to create an IO that wrote > to configurable sinks that might fit your use case > > On Sat, Aug 12, 2023 at 12:18 PM Bruno Volpato via dev < > dev@be

Mechanism for "Beam Website Feedback"

Hi all, We regularly get emails with "Subject: Beam Website Feedback", they are filtered out before they reach this mailing list. I believe the reason for that is people have some feedback to share, but clicking the feedback will open the default email application and they will be surprised and cl

Re: Beam IO Connector

Sure thing Jeremy, Generally, the workflow we do is that every one of our jobs takes a --consumerMode and/or --producerMode option and we pass those options to a Read and Write PTransform which wraps standard IO PTransforms and calls the correct one in expand based on the option's value. I have a

Re: Mechanism for "Beam Website Feedback"

Hi Ahmet, I'm +1 on the idea-- one clarification question: Do you propose that when feedback is sent, it gets forwarded to the dev list? If not, we will need to ensure that the backend (eg a Google sheet) is monitored. Svetak Sundhar Data Engineer s vetaksund...@google.com On Mon, Aug 14

Re: Mechanism for "Beam Website Feedback"

On Mon, Aug 14, 2023 at 1:48 PM Svetak Sundhar wrote: > Hi Ahmet, > > I'm +1 on the idea-- one clarification question: > > Do you propose that when feedback is sent, it gets forwarded to the dev > list? If not, we will need to ensure that the backend (eg a Google sheet) > is monitored. > I imagi

Re: [PROPOSAL] Preparing for 2.50.0 Release

Welcome to the Beam community! Our release managers usually follow this https://beam.apache.org/contribute/release-guide/#10-vote-and-validate-release-candidate to send the votes out and ask for any feedback regarding the release candidate. If you could help run any validation on your side and cast

Re: [PROPOSAL] Preparing for 2.50.0 Release

+1 to what XQ says. There will be a voting email thread once I've done the appropriate due diligence to the branch, and finish with the Dataflow artifacts. Generally speaking, the best validation is something you're using already, to make sure that the new version of Beam works for your usage.