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

Re: Automatic signing of releases

Yes, this is a great step forward (both the automation, and the clarified guidance). Hopefully we can automate virtual everything but the voting away. On Thu, Aug 24, 2023 at 8:56 AM Ismaël Mejía wrote: > Ah excellent, I was not aware it was the case, great to know we are in > advance ! > > On

Re: [PROPOSAL] Design Doc template for PTransforms

Thanks Kenn! I put up a PR to add this reference to the Beam website. I'm actively using the template now, and one piece of feedback I have is to include a section for prototyped work. Maybe a table that allows the user to post links to Github prototype

Re: Automatic signing of releases

Ah excellent, I was not aware it was the case, great to know we are in advance ! On Thu, Aug 24, 2023 at 4:54 PM Danny McCormick via dev wrote: > Hey Ismael, > > We've actually already been doing this since May! I started a thread for > this here

Re: Automatic signing of releases

Hey Ismael, We've actually already been doing this since May! I started a thread for this here https://lists.apache.org/thread/mw9dbbdjtkqlvs0mmrh452z3jsf68sct and its in an Actions workflow here -

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, > >

[Request for Feedback] Mechanism for "Beam Website Feedback"

Hi all, Following what Ahmet proposed here ( https://lists.apache.org/thread/9l18gs7vgqz6g1cfc2m66rbkrcnr9qmj), we changed the "SEED FEEDBACK" button to open the Google form (

[PROPOSAL] Design Doc template for PTransforms

Hi all, Based on some work I've been doing internally, I put together a public version of a design doc template for PTransforms. https://s.apache.org/ptransform-design-doc A major goal is to be explicit about important questions that make a transform robust: - what are "all" the parameters to

Re: [Request for Feedback] Swift SDK Prototype

Ah, that is a good point—being element-wise would make managing windows and time stamps easier for the user. Fortunately it’s a fairly easy change to make and maybe even less typing for the user. I was originally thinking side inputs and metrics would happen outside the loop, but I think you want

Re: [Request for Feedback] Swift SDK Prototype

I would like to figure out a way to get the stream-y interface to work, as I think it's more natural overall. One hypothesis is that if any elements are carried over loop iterations, there will likely be some that are carried over beyond the loop (after all the callee doesn't know when the loop

Re: [PROPOSAL] Design Doc template for PTransforms

+1 I'd love for this information to be accessible programmatically as well (both directions: extracting parameters from a transform and constructing a transform from parameters). Making this pattern easy could encourage compliance. On Thu, Aug 24, 2023 at 8:54 AM Svetak Sundhar via dev wrote:

[GitHub] [beam-site] lostluck opened a new pull request, #648: Update beam-site for release 2.50.0

lostluck opened a new pull request, #648: URL: https://github.com/apache/beam-site/pull/648 Content generated from commit bb044f4863cd151214f61174ac3c097bea724098. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

Re: [Request for Feedback] Swift SDK Prototype

Gotcha, I think there's a fairly easy solution to link input and output streams Let me try it out... might even be possible to have both element and stream-wise closure pardos. Definitely possible to have that at the DoFn level (called SerializableFn in the SDK because I want to use @DoFn as a

Re: [VOTE] Release 2.50.0, release candidate #2

Two minor erata from the previous email: The validation spreadsheet link should be: https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=1014811464 And the source code tag is: "v2.50.0-RC2" On 2023/08/24 23:09:23 Robert Burke wrote: > Hi everyone, >

[GitHub] [beam-site] lostluck closed pull request #647: Publish 2.50.0 release

lostluck closed pull request #647: Publish 2.50.0 release URL: https://github.com/apache/beam-site/pull/647 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

Re: [Request for Feedback] Swift SDK Prototype

On Thu, Aug 24, 2023 at 12:27 PM Robert Bradshaw wrote: > I would like to figure out a way to get the stream-y interface to work, as > I think it's more natural overall. > > One hypothesis is that if any elements are carried over loop iterations, > there will likely be some that are carried over

Re: [Request for Feedback] Swift SDK Prototype

On Thu, Aug 24, 2023 at 12:58 PM Chamikara Jayalath wrote: > > > On Thu, Aug 24, 2023 at 12:27 PM Robert Bradshaw > wrote: > >> I would like to figure out a way to get the stream-y interface to work, >> as I think it's more natural overall. >> >> One hypothesis is that if any elements are

[VOTE] Release 2.50.0, release candidate #2

Hi everyone, Please review and vote on the release candidate #2 for the version 2.50.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

Re: [Request for Feedback] Swift SDK Prototype

Ah, I see. Yeah, I've thought about using an iterable for the whole bundle rather than start/finish bundle callbacks, but one of the questions is how that would impact implicit passing of the timestamp (and other) metadata from input elements to output elements. (You can of course attach the

Re: Beam Website Feedback

Explicitly adding Jonas in case he is not subscribed to the dev list. On Thu, Aug 24, 2023 at 5:50 AM Kerry Donny-Clark via dev < dev@beam.apache.org> wrote: > 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

[ANNOUNCE] New committer: Ahmed Abualsaud

Hi all, Please join me and the rest of the Beam PMC in welcoming a new committer: Ahmed Abualsaud (ahmedabuals...@apache.org). Ahmed has been part of the Beam community since January 2022, working mostly on IO connectors, made a large amount of contributions to make Beam IOs more usable,

Re: [ANNOUNCE] New committer: Ahmed Abualsaud

Congratulations, Ahmed! On Thu, Aug 24, 2023, 5:49 PM Ahmet Altay via dev wrote: > Hi all, > > Please join me and the rest of the Beam PMC in welcoming a new > committer: Ahmed Abualsaud (ahmedabuals...@apache.org). > > Ahmed has been part of the Beam community since January 2022, working >

Re: [ANNOUNCE] New committer: Ahmed Abualsaud

Congratulations, Ahmed! Very well deserved! On Thu, Aug 24, 2023 at 6:09 PM XQ Hu via dev wrote: > Congratulations, Ahmed! > > On Thu, Aug 24, 2023, 5:49 PM Ahmet Altay via dev > wrote: > >> Hi all, >> >> Please join me and the rest of the Beam PMC in welcoming a new >> committer: Ahmed

Re: [ANNOUNCE] New committer: Ahmed Abualsaud

Congratulations! On Thu, Aug 24, 2023 at 5:34 PM Robert Burke wrote: > Congratulations Ahmed!! > > On Thu, Aug 24, 2023, 4:08 PM Chamikara Jayalath via dev < > dev@beam.apache.org> wrote: > >> Congrats Ahmed!! >> >> On Thu, Aug 24, 2023 at 4:06 PM Bruno Volpato via dev < >> dev@beam.apache.org>

Re: [ANNOUNCE] New committer: Ahmed Abualsaud

Well deserved! Congratulations, Ahmed! I'm so happy for you. On Thu, Aug 24, 2023, 5:46 PM Byron Ellis via dev wrote: > Congratulations! > > On Thu, Aug 24, 2023 at 5:34 PM Robert Burke wrote: > >> Congratulations Ahmed!! >> >> On Thu, Aug 24, 2023, 4:08 PM Chamikara Jayalath via dev < >>

Re: [ANNOUNCE] New committer: Ahmed Abualsaud

Congratulations Ahmed :) On Fri, Aug 25, 2023 at 1:17 AM Damon Douglas wrote: > Well deserved! Congratulations, Ahmed! I'm so happy for you. > > On Thu, Aug 24, 2023, 5:46 PM Byron Ellis via dev > wrote: > >> Congratulations! >> >> On Thu, Aug 24, 2023 at 5:34 PM Robert Burke wrote: >> >>>

Re: [Request for Feedback] Swift SDK Prototype

Okay, I tried a couple of different things. Implicitly passing the timestamp and window during iteration did not go well. While physically possible it introduces an invisible side effect into loop iteration which confused me when I tried to use it and I implemented it. Also, I'm pretty sure

Re: [ANNOUNCE] New committer: Ahmed Abualsaud

Congratulations Ahmed!! On Thu, Aug 24, 2023, 4:08 PM Chamikara Jayalath via dev < dev@beam.apache.org> wrote: > Congrats Ahmed!! > > On Thu, Aug 24, 2023 at 4:06 PM Bruno Volpato via dev > wrote: > >> Congratulations, Ahmed! >> >> Very well deserved! >> >> >> On Thu, Aug 24, 2023 at 6:09 PM XQ

Re: [ANNOUNCE] New committer: Ahmed Abualsaud

Congrats Ahmed!! On Thu, Aug 24, 2023 at 4:06 PM Bruno Volpato via dev wrote: > Congratulations, Ahmed! > > Very well deserved! > > > On Thu, Aug 24, 2023 at 6:09 PM XQ Hu via dev wrote: > >> Congratulations, Ahmed! >> >> On Thu, Aug 24, 2023, 5:49 PM Ahmet Altay via dev >> wrote: >> >>> Hi

Beam High Priority Issue Report (40)

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/28104 [Failing Test]:

Automatic signing of releases

Hi, I just saw an interesting change on the ASF side that could be of interest for Beam releases. The ASF now allows to do signing of releases by automated infrastructure. https://issues.apache.org/jira/browse/LEGAL-647 This is a good step for automation that I remember we discussed at the