Re: [ANNOUNCE] New committer: Yi Hu

Congratulations Yi! On Fri, Nov 11, 2022 at 1:57 PM Chamikara Jayalath via dev < dev@beam.apache.org> wrote: > Contrats Yi! > > On Thu, Nov 10, 2022 at 10:48 AM Kerry Donny-Clark via dev < > dev@beam.apache.org> wrote: > >> Great job Yi! I am happy to see your contributions recognized. >> >> On T

Re: [PROPOSAL] Preparing for Apache Beam 2.43.0 Release

Thank you! On Tue, Nov 8, 2022 at 1:39 PM Chamikara Jayalath wrote: > External artifacts have been built. I'm working on getting Dataflow > containers and documentation setup so should be out for review/vote soon :) > > On Tue, Nov 8, 2022 at 12:22 PM Ahmet Altay wrote: >

Re: [PROPOSAL] Preparing for Apache Beam 2.43.0 Release

gt; > On Fri, Nov 4, 2022 at 9:14 AM Ahmet Altay wrote: > >> Thank you Cham! >> >> On Thu, Nov 3, 2022 at 10:54 PM Chamikara Jayalath >> wrote: >> >>> Fix for the blocking issue was cherry-picked today. So I hope to build >>> the RC1 to

Re: github reviewer help / tips

On a related note: It is quite easy to miss GitHub notifications. If you are waiting on a review feel free to ping (github, email, slack etc.) the reviewer after a few days. On Tue, Nov 8, 2022 at 11:08 AM Pablo Estrada via dev wrote: > Nice pointer Valentyn. > > If you are willing to open the G

Re: [ANNOUNCE] New committer: Ritesh Ghorse

Congratulations Ritesh! On Fri, Nov 4, 2022 at 12:18 PM Ritesh Ghorse via dev wrote: > Thanks everyone! I'm glad to be a part of this community and I look > forward to making more contributions in whatever ways I can. > > On Fri, Nov 4, 2022 at 12:36 PM Chamikara Jayalath via dev < > dev@beam.ap

Re: [PROPOSAL] Preparing for Apache Beam 2.43.0 Release

Thank you Cham! On Thu, Nov 3, 2022 at 10:54 PM Chamikara Jayalath wrote: > Fix for the blocking issue was cherry-picked today. So I hope to build the > RC1 tomorrow. > > Thanks, > Cham > > On Thu, Nov 3, 2022 at 8:19 PM Ahmet Altay wrote: > >> How is the release

Re: [PROPOSAL] Preparing for Apache Beam 2.43.0 Release

as cut: >>> https://github.com/apache/beam/tree/release-2.43.0 >>> >>> We currently have three open blockers in the release milestone: >>> https://github.com/apache/beam/milestone/5 >>> >>> I'll look into cherry-picking fixes for these an

Re: SSL issue: Kafka Avro write with Schema Registry (GCP)

(moving this to the user list, dev list to bcc.) Adding relevant people: @John Casey . (Keshav, for Dataflow issues you could also reach out to Dataflow support: https://cloud.google.com/dataflow/docs/support) On Mon, Oct 31, 2022 at 1:23 PM Chennakeshavlu Maddela < chennakeshavlu.madd...@davita

Re: [Proposal] Beam MultimapState API

Thank you for the message Buqian. Adding @Reuven Lax @Lukasz Cwik explicitly (who are mentioned on the doc). On Mon, Oct 31, 2022 at 12:17 PM 郑卜千 wrote: > Gentle ping. Thanks! > > On Thu, Oct 27, 2022 at 2:55 PM 郑卜千 wrote: > >> Hi all, >> >> I've been working on adding MultimapState support t

Re: Beam Website Feedback: Apache Beam WordCount Examples

Thank you for reporting William. Adding @Valentyn Tymofieiev . Perhaps we could start with creating an issue? On Mon, Oct 24, 2022 at 9:25 AM William Pietri wrote: > Hi! I have inherited code using Apache Beam and I'm trying to figure out > the right way to use it. > > This seemed like it would

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

+1 (binding) Tested python quickstart examples on the direct runner. Thank you! On Thu, Oct 13, 2022 at 5:35 PM Robert Bradshaw via dev wrote: > +1 (binding) > > Validated release artifacts and signatures. Tested a Python pipeline > on a clean install. > > On Thu, Oct 13, 2022 at 1:22 PM Ritesh

Re: [PROPOSAL] Preparing for Apache Beam 2.43.0 Release

+1 - Thank you Cham! On Wed, Oct 5, 2022 at 1:38 PM Chamikara Jayalath via dev < dev@beam.apache.org> wrote: > Hi all, > > The next (2.43.0) release branch cut is scheduled for October 19th, > according to the release calendar [1]. > > I would like to volunteer myself to do this release. My plan

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

+1 (binding) - I validated python quick starts on direct runner. Thank you for working on the release! Ahmet On Mon, Oct 3, 2022 at 9:06 AM Valentyn Tymofieiev via dev < dev@beam.apache.org> wrote: > I validated that Dataflow and Beam Python containers have dependencies > that match Beam requir

Re: Rest connector

/cc @John Casey On Mon, Sep 12, 2022 at 12:03 PM Reddy annapureddy, Vijayas (V.) < vredd...@ford.com> wrote: > Hi Team, > > We are planning to use Apache beam for a new microservice project which is > in the discovery phase. Apache beam pipeline will read data from GCS and > send data to other

Re: Beam Website Feedback

Thank you for the feedback Peter. /cc @Reza Rokni @David Cavazos for visibility. On Fri, Sep 9, 2022 at 2:51 PM Austin Bennett wrote: > Any chance you've seen a GH Issue for that? If not, please feel free to > file one :-) > > https://github.com/apache/beam/issues > > On Fri, Sep 9, 2022 at

Re: [ANNOUNCE] Apache Beam 2.41.0 Released

Thank you Kiley! On Fri, Aug 26, 2022 at 6:38 AM P Singh wrote: > Hi Team, > > Looking forward to trying and testing the new version, It's always > fascinating. > > On Fri, 26 Aug 2022 at 03:45, Pablo Estrada via user > wrote: > >> Thank you Kiley! >> >> On Thu, Aug 25, 2022 at 10:55 AM Kiley S

Re: Java & Python Project Starter / Example Using Terraform to build Dataflow Custom Templates

Thank you for sharing Damon. On Tue, Aug 23, 2022 at 9:34 AM Damon Douglas via dev wrote: > Hello Everyone, > > You can ignore this email if you do not use the Dataflow runner. > > We just published an example / project starter that shows how to build > Dataflow Custom Templates provisioned usin

Re: Beam Website Feedback

Thank you Tianzi. Adding relevant folks: @John Casey On Mon, Aug 22, 2022 at 3:03 PM Tianzi Cai via dev wrote: > According to this page, > https://beam.apache.org/documentation/io/connectors/, KinesisIO doesn't > have Python implementation, but I found > https://beam.apache.org/releases/pydoc/

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

+1 - I valited python quickstarts on the directrunner. Thank you Kiley! On Thu, Aug 18, 2022 at 1:31 PM Kiley Sok via dev wrote: > Hi everyone, > Please review and vote on the release candidate #1 for the version 2.41.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the re

Re: Forward StackOverflow questions with the apache-beam tag to a new mailing list

+1 to this idea. I think both options are reasonable. At the same time I also agree with checking with infra first on the feasibility of creating another mailing list. On Wed, Aug 17, 2022 at 10:00 AM Chamikara Jayalath wrote: > > > On Wed, Aug 17, 2022 at 9:18 AM Robert Bradshaw > wrote: > >>

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

+1 - I validated python quickstarts on direct runner. Thank you Kiley! On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev wrote: > Hi everyone, > Please review and vote on the release candidate #1 for the version 2.41.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the

Re: Community event cooperation

;> Both parties will invest resources to hold this technical exchange meetup, >>>> collide with the developers on speech topics, and promote together, and we >>>> will give the greatest support in China. This event, let more developers >>>> know about Apache Bea

Re: Community event cooperation

Hi Niko, Thank you for reaching out. We do have contributors who might be interested in participating but they might have limited time for participating in an event. If you can clarify what are you looking for (e.g. speaker? help with coordination? etc.) people might be able to give you a better a

Re: [Release] 2.41.0 release update

Kiley, do we still have the same blockers? Do you need any help? On Thu, Aug 4, 2022 at 12:18 PM Kiley Sok via dev wrote: > Last remaining issue was cherry-picked. There may be one last issue with > gRPC that's being investigated. > > https://github.com/apache/beam/issues/22283 > > On Thu, Jul 2

Re: [ANNOUNCE] New committer: John Casey

Congratulations John! On Fri, Jul 29, 2022 at 2:03 PM Svetak Sundhar via dev wrote: > Congrats John!! > > > Svetak Sundhar > > Technical Solutions Engineer, Data > s vetaksund...@google.com > > > > On Fri, Jul 29, 2022 at 5:02 PM Ritesh Ghorse via dev > wrote: > >> Congratulations John! >> >>

Re: [ANNOUNCE] New committer: Steven Niemitz

Congratulations Steve! On Thu, Jul 21, 2022 at 10:31 AM Steve Niemitz via dev wrote: > Thanks everyone! > > On Thu, Jul 21, 2022 at 2:23 AM Moritz Mack wrote: > >> Congrats, Steven! >> >> >> >> On 21.07.22, 05:25, "Evan Galpin" wrote: >> >> >> >> Congrats! Well deserved! On Wed, Jul 20, 2022 a

Re: Extending 2.41.0 Java snapshot TTL

Thank you for the email Daniel. Adding people who could help: @Kenneth Knowles @Danny McCormick @Chamikara Jayalath @John Casey @Byron Ellis On Thu, Jul 21, 2022, 4:14 PM Daniel Thevessen via dev wrote: > Hi all, > > The Java Firestore connector had a bug >

Re: Beam Website Feedback

Thank you for reporting. https://github.com/apache/beam/pull/15671 would fix the issues you mentioned. On Wed, Oct 6, 2021 at 2:56 PM Mike Stayton wrote: > Your contact-us page has some bad links > > https://beam.apache.org/community/contact-us/ > Subsribe and Unsubscribe: > > Prior to sending e

Re: [Proposal] Default tempDirectory setting in file-based IOs

Adding relevant folks +Chamikara Jayalath +Pablo Estrada This proposal makes sense to me. It makes it easier for users to reason about why a temp directory is chosen, and would lead to a unified code across all IOs that does this. On Thu, Sep 9, 2021 at 11:37 AM Claire McGinty wrote: > Hi Bea

Re: Beam Website Feedback

Thank you and I filed https://issues.apache.org/jira/browse/BEAM-12682 to track this. (/cc @David Huntsperger ) Related question to everyone, do we have a process for the "Beam Website Feedback" emails? I see these emails occasionally, and some of them are for trivial issues and addressed quickly

Re: Avro String decoding changes in Beam 2.30.0

an opinion: /cc @Ismaël Mejía @Kenneth Knowles @Lukasz Cwik +Vitaly > > Thanks, > Claire > > On Tue, Jul 20, 2021 at 4:15 PM Ahmet Altay wrote: > >> Is this something we need to add to the 2.30.0 release notes ( >> https://beam.apache.org/blog/beam-2.30.0/) as a bre

Re: [NEED HELP] PMC only finalization items for release 2.30.0

I helped Heejong with this, Heejong let us know if you need anything else related to this. On Wed, Jun 9, 2021 at 10:15 PM Heejong Lee wrote: > Hi, > > I'm finishing 2.30.0 release and need help doing PMC only finalization > items in the release guide ( > https://beam.apache.org/contribute/relea

Re: Lots of VMs

Update: I stopped beam-jenkins-clang-format and new-ci-node-test. Other instances from my first email were already stopped. Thank you for doing that. And if you need any one of these instances to run, feel free to start them again. Ahmet On Thu, May 27, 2021 at 4:54 PM Ahmet Altay wrote

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

+1 (binding) - I ran python quickstart examples on the direct runner. Thank you for preparing the RC! Ahmet On Thu, Jun 3, 2021 at 2:58 PM Chamikara Jayalath wrote: > +1 (binding) > > Tested some Java quickstart validations and multi-language pipelines. > > Thanks, > Cham > > On Thu, Jun 3, 20

Re: [Question] Best Practice of Handling Null Key for KafkaRecordCoder

/cc folks who commented on the issue: @Robin Qiu @Chamikara Jayalath @Alexey Romanenko @Daniel Collins On Tue, Jun 1, 2021 at 2:03 PM Weiwen Xu wrote: > Hello, > > I'm working on [this issue]( > https://issues.apache.org/jira/browse/BEAM-12008) with Boyuan. She was > very helpful in identif

Re: Missing copyright notices due to LICENSE change

cherrypick licence textual fixes into the older >> versions for the licence matching, then the site will pick those up again. >> 2. Users can run the godoc tool >> <https://pkg.go.dev/golang.org/x/tools/cmd/godoc> themselves to get >> package documentation if they want

Re: [NEED HELP] Populating the change list for 2.30.0 release

Feel free to use whatever is already in the changes.md under the 2.30.0 section. We can always update this, during voting, even after the release. On Thu, May 27, 2021 at 11:50 AM Heejong Lee wrote: > Hi Beam developers, > > I'm gathering the information for the changes in the 2.30.0 release. If

Re: Lots of VMs

Folks, I will stop the VMs I listed in my first email sometime next week. Feel free to resume them if you need them. And if you have any other unused VMs please stop or delete them. Thank you, Ahmet On Mon, May 10, 2021 at 10:08 AM Ahmet Altay wrote: > That is a good suggestion. I can do t

Re: Compatibility Check Badges need attention

Is this compatibility checking tool still supported? If not, maybe we can remove these badges? On Wed, May 19, 2021 at 2:43 PM Lily Li wrote: > I have not worked on this project for quite some time. > > +Colin Nelson > > On Tue, May 18, 2021 at 4:00 PM Valentyn Tymofieiev > wrote: > >> Looks l

Re: [PROPOSAL] Preparing for Beam 2.31.0 release

+1. Thank you Andrew. On Thu, May 20, 2021 at 1:15 PM Andrew Pilloud wrote: > Hi All, > > Beam 2.31.0 release is scheduled to be cut in two weeks, on June 2 > according to the release calendar [1]. > > I'd like to volunteer myself to be the release manager for this release. I > plan on cutting t

Re: Inaccessible CI-built python SDK artifact on GCS staging bucket (individual wheels are accessible)

Moving to dev list. This looks like a bug in the build workflow but I cannot pinpoint it. In the GCS UI all objects have Public Access: Not Authorized property. This explains why you cannot download them. However workflow uses "gsutil cp -r -a public-read ..." to copy the object to GCS, and "-a pu

Re: Removing deprecated oauth2client dependency for Python SDK

+Valentyn Tymofieiev might have an idea. On Mon, May 3, 2021 at 4:12 PM Chuck Yang wrote: > Hi Beam devs, > > I saw there has been some previous discussion [1][2] around removing > the deprecated oauth2client dependency and using the supported > google-auth dependency instead. A portion of this

Re: Transform-specific thread pools in Python

On Mon, May 10, 2021 at 8:01 AM Stephan Hoyer wrote: > Hi Beam devs, > > I've been exploring recently how to optimize IO bound steps for my Python > Beam pipelines, and have come up with a solution that I think might make > sense to upstream into Beam's Python SDK. > > It appears that Beam runner

Re: Flake trends - better?

now of only two severe flakes >>> (that you can count on seeing in a day/week). If so, then more cleanup >>> would be valuable. This is why I ran the second report: I suspected that we >>> had a lot of very old stale flake bugs that noone is looking at. >>> >&

Lots of VMs

Hello, It looks like we have accumulated a bunch of running VMs with very low utilization. Some of them have temp, test etc. in their names and probably no longer needed. If you started a one time use only VM and no longer need it could you stop or delete those? A few that could be potentially de

Lots of branches

Hello all, Our git repo has lots of branches for cherry picks, patches, reverts etc. I believe these are artifacts of github's easy to use online editor. If you no longer need those, could you please clean them? Have a great weekend! Ahmet

Re: Flake trends - better?

Thank you for sharing the charts. I know you are the messenger here, but I disagree with the message that flakes are getting noticeably better. Number of open issues look quite large but at least stable. I will guess that some of those are stale and seemingly we did a clean up in July 2020. We can

Re: Consider Cloudpickle instead of dill for Python pickling

I agree with Robert on this one. With the exception of DillCoder, it might be reasonable to conditionally support both. (On a related note, I only see one use of DillCoder, do we really need that coder?) On Mon, May 3, 2021 at 5:01 AM Kenneth Knowles wrote: > My 2 contradictory cents from even f

Re: Beam Jira Contribution rights

Done. Welcome! On Fri, Apr 30, 2021 at 4:30 PM Daniel Thevessen wrote: > Hi everyone, > > This is Daniel, I'm an SRE for Cloud Firestore. I've been involved in the > development of the FirestoreIO connector and would like to assign a few > tickets for related work on the Datastore connector. Cou

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

+1 (binding) I ran some python quick start examples. Most validations in the sheet were already done :) Thank you all! On Thu, Apr 22, 2021 at 9:15 AM Kyle Weaver wrote: > +1 (non-) > > Ran Python wordcount on Flink and Spark. > > On Wed, Apr 21, 2021 at 5:20 PM Brian Hulette wrote: > >> +1 (n

Re: [ANNOUNCE] New committer: Yichi Zhang

Congratulations Yichi! 📣📣📣 On Wed, Apr 21, 2021 at 6:48 PM Chamikara Jayalath wrote: > Congrats Yichi! > > On Wed, Apr 21, 2021 at 6:14 PM Heejong Lee wrote: > >> Congratulations :) >> >> On Wed, Apr 21, 2021 at 5:20 PM Tomo Suzuki wrote: >> >>> Congratulations! >>> >>> On Wed, Apr 21, 2021 at

Re: [PROPOSAL] Preparing for Beam 2.30.0 release

+1 and thank you! On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee wrote: > Hi All, > > Beam 2.30.0 release is scheduled to be cut on April 21 according to the > release calendar [1] > > I'd like to volunteer myself to be the release manager for this release. > I plan on cutting the release branch on

Re: Codecov Bash Uploader Security Notice

I received the same email too. I think it is related to Beam given that we all received it. I cannot find any references to the bash uploader anymore but I found some references from 2016 [1]. It looks like we used it at some point in the past and maybe that is why we received the notifications. If

Re: [ANNOUNCE] New committer: Tomo Suzuki

Congratulations! 🎉🎉🎉 On Fri, Apr 2, 2021 at 9:38 AM Kenneth Knowles wrote: > Hi all, > > Please join me and the rest of the Beam PMC in welcoming a new committer: > Tomo Suzuki > > Since joining the Beam community in 2019, Tomo has done lots of critical > work on Beam's dependencies: maintaining

Re: [DISCUSS] Jira isssue type: "Support"

+1 on using a label instead. I think the naming will matter. "Support" might send a wrong message, but "User Issue" sounds more neutral and would necessarily set an expectation to receive support. (I have no data to "support" this :), it is a guess.) Would it be possible to somehow link user@ list

Re: [Apace BEAM Go improvements] Lazy map side inputs

Adding some folks who might be able to help: @Robert Burke @Kenneth Knowles @Tyson Hamilton On Mon, Mar 29, 2021 at 2:31 PM Miguel Anzo Palomo wrote: > Hi, > I was checking out this task BEAM-3293 > and I'm having some > issues fully understa

Re: Hi Team

Welcome Uday! On Mon, Mar 29, 2021 at 11:23 AM Uday Singh wrote: > Hi Everyone, > > This is Uday and i will be working on Apache Beam from GCP dataflow team. > Looking forward to contributing to the community. > > Thanks > Uday >

Re: Contributor permission for Jira tickets

Done. Welcome. On Thu, Mar 25, 2021 at 3:39 AM Fabien Caylus wrote: > Hi ! > > I'm sorry for this second message. But I realized that my first one was > detected as spam by gmail, because I used the Pony Mail interface to send > it ... > So I believed it may have been detected as spam for others

Re: Make KafkaIO usable from Dataflow Template?

On Wed, Mar 24, 2021 at 10:58 AM Alexey Romanenko wrote: > Robert, could you elaborate a bit why or point me out if it was already > discussed? > I will speak to this from a Dataflow perspective. As Alex pointed out above Dataflow's flex templates allows for a more flexible (:p) way of creating

Re: BEAM-9185 Publish pre-release python artifacts (RCs) to PyPI

This looks like a good and reasonable approach to me. I have not reviewed the PR, but I agree with outlined modifications. It will be good to get reviews from +Valentyn Tymofieiev (who has lots of experience in this area) and +Kenneth Knowles (who is the current release manager to understand how

Re: BEAM-3713: Moving from nose to pytest

All PRs look either merged or closed. +Udi Meiri might have more information about the remaining work. On Wed, Mar 24, 2021 at 5:29 PM Benjamin Gonzalez Delgado < benjamin.gonza...@wizeline.com> wrote: > Hi team, > I am planning to work in BEAM-3713 >

Re: [ANNOUNCE] New committer: Ning Kang

Congratulations Ning! On Tue, Mar 23, 2021 at 12:38 PM Alexey Romanenko wrote: > Congrats, Ning Kang! Well deserved! > Thank you for your contributions and users support! > > Alexey > > On 23 Mar 2021, at 20:35, Pablo Estrada wrote: > > Hi all, > > Please join me and the rest of the Beam PMC in

Re: Missing copyright notices due to LICENSE change

se. I guess that makes me +0 for cherrypick. >> >> Brian >> >> On Mon, Mar 22, 2021 at 10:43 AM Ahmet Altay wrote: >> >>> >>> >>> On Mon, Mar 22, 2021 at 10:31 AM Kenneth Knowles >>> wrote: >>> >>>> Is the

Re: Missing copyright notices due to LICENSE change

ot included in >> https://github.com/apache/beam/blob/master/LICENSE. Is that WAI since >> Dataflow runner is released as a separate jar artifact, and the licenses in >> question (GPL 2.0, CDDL) pertain to its dependencies, or we need to include >> those licenses as well? >&

Re: Contributor permission for Beam Jira tickets

Done. Welcome. On Mon, Mar 22, 2021 at 9:12 AM Vitaly Terentyev < vitaly.terent...@akvelon.com> wrote: > Hello, looks like I haven't received a reply letter. > Here is my Jira username: R3tto. > > Best regards, > > Vitaly > > From: Vitaly Terentyev > Sent:

Re: Beam Website Feedback

On Mon, Mar 15, 2021 at 5:51 AM Brian Hulette wrote: > Hm thanks for pointing this out Brian. It looks like the Java > WindowedWordCount example does process an input file while the Java one > processes a PubSub topic. Changing the command would be a good quick fix, > but I think the best fix wou

Re: Please review P0 and P1 bugs you are assigned or you filed

Thank you for the ping Kenn. I was able to close 4 issues and now I see 95 P0/P1 issues. I guess we did not make much of a dent in the backlog. On Fri, Mar 12, 2021 at 4:00 PM Kenneth Knowles wrote: > Hi all, > > There are 97 P1 or P0 bugs open [1]. > > Quoting https://beam.apache.org/contribute

Re: Missing copyright notices due to LICENSE change

rther clarification. > > On Wed, Mar 17, 2021 at 7:49 PM Ahmet Altay wrote: > >> Thank you Rebo. I agree with reverting first and then figure out the next >> steps. >> >> Here is a PR to revert your change: >> https://github.com/apache/beam/pull/14267 >&

Re: Missing copyright notices due to LICENSE change

PSF license. However it is a redistribution > friendly license, which is what matters. > > On Wed, Mar 17, 2021, 3:00 PM Ahmet Altay wrote: > >> Thank you for this email. >> >> >> On Wed, Mar 17, 2021 at 2:32 PM Brian Hulette >> wrote: >> >>>

Re: Missing copyright notices due to LICENSE change

Thank you for this email. On Wed, Mar 17, 2021 at 2:32 PM Brian Hulette wrote: > I just noticed that there was a recent change to our LICENSE file to make > it exactly match the Apache 2.0 License [1]. This seems to be the result of > two conflicting LICENSE issues. > > Go LICENSE issue: The mo

Re: [VOTE] Vendored Dependencies Release gRPC 1.36.0 v0.1 RC1

+1 On Tue, Mar 16, 2021 at 4:21 PM Robert Bradshaw wrote: > +1 > > On Tue, Mar 16, 2021 at 4:00 PM Kenneth Knowles wrote: > >> Please review the release of the following artifacts that we vendor: >> * beam-vendor-grpc-1_36_0 >> >> Hi everyone, >> >> Please review and vote on the release candid

Re: User-related questions in dev@ list

On Wed, Mar 10, 2021 at 11:16 AM Alexey Romanenko wrote: > > > What do you think should be the right behaviour for managing such emails? >> Forward this email to user@ (and remove dev@ address from copy) and ask >> politely to continue a discussion there? I tried it several times but >> sometimes

Re: User-related questions in dev@ list

On Wed, Mar 10, 2021 at 10:36 AM Alexey Romanenko wrote: > Hello all, > > A quick question about our mailing lists policy. > > Quite often I see that people tend to send the user-related questions to > dev@. For example: [1], [2] and many similar ones. > > I believe it’s a bad practice since it's

Re: Add oozer to JIRA contribution list

Done. Welcome! On Tue, Mar 9, 2021 at 8:05 PM Onur Ozer wrote: > Hi There, > > Could you please add me as a contributor to ASF JIRA. My username is oozer. > > Thanks, >

Re: Add ebarrera to JIRA contributor list

Done. Welcome! On Tue, Mar 9, 2021 at 11:22 AM Eduardo Barrera < eduardo.barr...@wizeline.com> wrote: > Hello team, > > Can you please add 'ebarrera' to the JIRA contributor list? > > Thanks! > Eduardo > > > > > > > > > *This email and its contents (including any attachments) are being sent > toy

Re: [VOTE] Release vendor-calcite-1_26_0 version 0.1, release candidate #1

+1 (binding) On Mon, Mar 8, 2021 at 3:21 PM Pablo Estrada wrote: > +1 (binding) verified signature > > On Mon, Mar 8, 2021 at 12:05 PM Kai Jiang wrote: > >> +1 (non-binding) >> >> On Mon, Mar 8, 2021 at 11:37 AM Andrew Pilloud >> wrote: >> >>> Hi everyone, >>> Please review and vote on the rel

Re: March 2021, Beam Community Update

Good update, thank you for sharing. The date in the header needs to be updated, it says October. I think it would make sense to distribute this update to user@ list as well. And we might get more readership if the contents are sent directly in the email. On Fri, Mar 5, 2021 at 12:10 PM Brittany He

Re: Review request for 2 Python BigQuery IO related PRs

+Pablo Estrada On Wed, Mar 3, 2021 at 1:08 PM Chuck Yang wrote: > Hi Beam devs, > > Could I have reviews on the following two PRs? > > * [BEAM-11884] Pass destination as str rather than TableReference > within BigQueryBatchFileLoads #14112 [1] > * [BEAM-11277] Respect schemaUpdateOptions during

Re: [PROPOSAL] Preparing for Beam 2.29.0 release

+1 and thank you! On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles wrote: > Hi All, > > Beam 2.29.0 release is scheduled to be cut in a week, on March 10 > according to the release calendar [1]. > > I'd like to volunteer myself to be the release manager for this release. > I plan on cutting the r

Re: BEAM-6855

Hemali, would this be a reasonable workaround for your problem? /cc +Kenneth Knowles - In case there is an alternative workaround to BEAM-6855. /cc +Cosmin Arad On Thu, Feb 18, 2021 at 1:27 PM Brian Hulette wrote: > I added JvmInitializer [1] to do some one-time initialization per JVM > befor

Re: [Proposal] Requesting PMC approval to start planning for Beam Summits 2021

On Thu, Feb 11, 2021 at 5:26 PM Brittany Hermann wrote: > Nothing substantial. Only change is going from a half day, five day event > to a 3 day full day event. > Out of curiosity, what is the reason for changing the format from half days to full days? > > On Thu, Feb 11, 2021 at 7:24 PM Rober

Re: [Proposal]: Add concepts guide and glossary to docs

This is a great idea. I would encourage others to look at the list of glossary items and see if anything interesting is missing from the list. On Wed, Feb 10, 2021 at 3:15 PM David Huntsperger wrote: > Feedback welcome: > >- [Proposal] Beam concepts & glossary > >

Re: Builds Meeting this Thursday

apache.org%3E > > > On Mon, Feb 8, 2021 at 2:56 PM Ahmet Altay wrote: > >> Thank you for sharing this Ismaël. >> >> This 180 jobs limit across all Apache projects sounds like a problem for >> Beam, because we are running quite a bit of GH actions already. Following

Re: [Vote] Publishing new website designs

+1 - I did a basic review looking around python docs and release guides mostly. One thing I would like to see fixed related to https://beam.apache.org/community/powered-by/ - New page is missing existing items from the current list https://beam.apache.org/community/powered-by/. Particularly I coul

Re: Builds Meeting this Thursday

Thank you for sharing this Ismaël. This 180 jobs limit across all Apache projects sounds like a problem for Beam, because we are running quite a bit of GH actions already. Following the Airflow suggestions, we can add VMs to apache-beam-testing projects to add Beam specifici private runners to add

Re: [Proposal] Release Guide improvements

Thanks a lot for doing this! :) It is a good improvement. On Tue, Jan 26, 2021 at 4:12 PM Robert Burke wrote: > Dang it. Good catch. Thanks. > https://issues.apache.org/jira/browse/BEAM-11693 is the right JIRA. > > On Tue, Jan 26, 2021 at 3:56 PM Robert Burke wrote: > >> Hello Beamers! >> >> I

Re: KafkaIO withStartReadTime hard failure

+Boyuan Zhang - in case she knows the answer. On Wed, Jan 27, 2021 at 9:30 AM Alexey Romanenko wrote: > + Raghu Angadi > > Raghu, I guess you did a review of the PR with this feature. > Could you shed some light on this, please? > > Alexey > > On 25 Jan 2021, at 13:59, Dan Mason wrote: > > Hi

Re: [ANNOUNCE] New committer: Piotr Szuberski

Congratulations Piotr! On Fri, Jan 22, 2021 at 11:21 AM Chamikara Jayalath wrote: > Congrats Piotr! > > On Fri, Jan 22, 2021 at 11:19 AM Valentyn Tymofieiev > wrote: > >> Congrats, Piotr! >> >> On Fri, Jan 22, 2021 at 11:12 AM Rui Wang wrote: >> >>> Congrats! >>> >>> >>> -Rui >>> >>> On Fri, J

[ANNOUNCE] New PMC Member: Chamikara Jayalath

Hi all, Please join me and the rest of Beam PMC in welcoming Chamikara Jayalath as our newest PMC member. Cham has been part of the Beam community from its early days and contributed to the project in significant ways, including contributing new features and improvements especially related Beam I

Re: Access to apache-beam-testing project

Hi. I added you to the project. On Wed, Jan 20, 2021 at 2:35 PM Milena Bukal wrote: > Hi! > > Can I have permissions for the project "apache-beam-testing" to run FhirIO > integration tests? > > Thanks! > Milena >

Re: Upgrading non-vendored Guava version

+Kenneth Knowles +Tyson Hamilton +Kiley Sok On Thu, Jan 14, 2021 at 4:23 PM Tomo Suzuki wrote: > Hi Beam developers, > > I'm preparing a pull request (#13740) > that upgrades the > non-vendored Guava version (currently 25.1-jre) to the latest versio

Re: [PROPOSAL] Preparing for Beam 2.28.0 release

Thank you Cham! On Wed, Jan 13, 2021 at 12:44 PM Rui Wang wrote: > Thanks Cham for working on this! > > > -Rui > > On Wed, Jan 13, 2021 at 11:32 AM Kyle Weaver wrote: > >> Thanks for stepping up Cham! >> >> Remember to mark critical JIRA issues as release blockers everybody! >> >> On Wed, Jan 1

Re: Contributor permission for Beam Jira

Done. Welcome! On Wed, Jan 13, 2021 at 1:56 AM Raphael Sanamyan < raphael.sanam...@akvelon.com> wrote: > Hi, I am Raphael from Akvelon. > > I would like to be a beam contributor. > Could you please add me as a contributor to Beam's Jira issue tracker? I > would like to create/assign tickets? > >

Re: [ANNOUNCE] Beam 2.27.0 Released

Thank you Pablo! On Fri, Jan 8, 2021 at 1:20 PM Pablo Estrada wrote: > The Apache Beam team is pleased to announce the release of version 2.27.0. > > Apache Beam is an open source unified programming model to define and > execute data processing pipelines, including ETL, batch and stream > (cont

Re: pulllicenses fails while building

Googled this a bit. Setting this env variable might fix the problem by bypassing the check: export PYTHONHTTPSVERIFY=0 Could you try that? If it works we can make that part of the script. Also, I am not sure why licenses are pulled for regular development case. I thought it was not meant to run b

Re: Website is MIT licensed?

I agree with you. I guess we missed this during the website migration. https://github.com/apache/beam/pull/13698 is to fix. On Thu, Jan 7, 2021 at 12:42 PM Kyle Weaver wrote: > Hi all, > > I discovered the Beam website's NPM module purports to be MIT licensed > [1]. I don't think we publish the

Re: Why are all the website files failing RAT?

On Thu, Jan 7, 2021 at 3:35 PM Brian Hulette wrote: > > > On Thu, Jan 7, 2021 at 2:00 PM Ahmet Altay wrote: > >> >> >> On Thu, Jan 7, 2021 at 12:25 PM Kyle Weaver wrote: >> >>> I repro'd this by running "./gradlew :rat". If I unders

Re: Why are all the website files failing RAT?

On Thu, Jan 7, 2021 at 12:25 PM Kyle Weaver wrote: > I repro'd this by running "./gradlew :rat". If I understand correctly, > these are all Hugo dependencies that are downloaded automatically. I looked > at a few of them and they do have licenses, but I guess rat just doesn't > recognize them for

Re: [VOTE] Release 2.27.0, release candidate #4

+1 (binding) - validated python quickstarts. Thank you Pablo. On Wed, Jan 6, 2021 at 1:57 PM Pablo Estrada wrote: > +1 (binding) > I've built and unit tested existing Dataflow Templates with the new > version. > Best > -P. > > On Tue, Jan 5, 2021 at 11:17 PM Pablo Estrada wrote: > >> Hi everyo

Re: Contributor Permissions

I added you as a contributor. You can self assign the jira to yourself. Welcome and thank you for contributing. On Wed, Jan 6, 2021 at 3:22 PM John Edmonds wrote: > I'm interested in taking on a small issue I created ( > https://issues.apache.org/jira/browse/BEAM-11580). Could I have > permissio

<    1   2   3   4   5   6   7   8   9   10   >