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.

Re: Add Member

Welcome! I added Jira user pawas2...@gmail.com to the "Contributors" role so you can be assigned tickets. Kenn On Thu, May 27, 2021 at 5:18 PM Pawas Chhokra wrote: > Hi Beam Team, > > I am working for the Samza team at LinkedIn and I would like to contribute > to the Samza Runner in Beam. My

Re: [DISCUSS] Client SDK/Job Server/Worker Pool Lifecycle Management on Kubernetes

Good to know. We are working on running java portable pipeline for Samza runner and I believe we could take on the task to enhance the java workflow to support timeout/retry etc on gRPC calls. Created BEAM-12419 to track the work. Best, Ke

Add Member

Hi Beam Team, I am working for the Samza team at LinkedIn and I would like to contribute to the Samza Runner in Beam. My GitHub username is *PawasChhokra*. Could I please get the permission to add/assign tickets in the Beam Jira? Thanks & Regards, Pawas Chhokra

Re: Out of band pickling in Python (pickle5)

I'm unlikely to have bandwidth to take this one on, but I do think it would be quite valuable! On Thu, May 27, 2021 at 4:42 PM Brian Hulette wrote: > I filed https://issues.apache.org/jira/browse/BEAM-12418 for this. Would > you have any interest in taking it on? > > On Tue, May 25, 2021 at

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 that

Re: Out of band pickling in Python (pickle5)

I filed https://issues.apache.org/jira/browse/BEAM-12418 for this. Would you have any interest in taking it on? On Tue, May 25, 2021 at 3:09 PM Brian Hulette wrote: > Hm this would definitely be of interest for the DataFrame API, which is > shuffling pandas objects. This issue [1] confirms what

Re: [DISCUSS] Client SDK/Job Server/Worker Pool Lifecycle Management on Kubernetes

I don't think there's any specific reason we don't set a timeout, I'm guessing it was just never worth the effort of implementing. If it's stuck it should be pretty obvious from the logs: "Still waiting for startup of environment from {} for worker id {}" On Thu, May 27, 2021 at 4:04 PM Ke Wu

Re: [DISCUSS] Client SDK/Job Server/Worker Pool Lifecycle Management on Kubernetes

Hi Kyle, Thank you for the prompt response and apologize for the late reply. [1] seems to be only available in python portable_runner but not java PortableRunner, is it intended or we could add similar changes in java as well? [2] makes sense to block since the wait/retry is handled in the

Re: One Pager - Test Command Line Discoverability in Beam

On Wed, May 26, 2021 at 5:05 PM Kyle Weaver wrote: > (I assume the "job_" prefix is arbitrary; I'm not sure why we use a >> filename prefix instead of a proper subfolder). >> > Tangent: Totally agree this is odd. I believe it was because we failed to figure out how to import utility libraries

[NEED HELP] Populating the change list for 2.30.0 release

Hi Beam developers, I'm gathering the information for the changes in the 2.30.0 release. If you have any idea about important *new features* / *breaking changes* / *deprecation* / *known issues* for the 2.30.0 release, please note down them in CHANGES.md or just let me know. Thanks!

Flaky test issue report (40)

This is your daily summary of Beam's current flaky tests (https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20labels%20%3D%20flake) These are P1 issues because they have a major negative impact on the community and make it hard to

P1 issues report (39)

This is your daily summary of Beam's current P1 issues, not including flaky tests (https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20priority%20%3D%20P1%20AND%20(labels%20is%20EMPTY%20OR%20labels%20!%3D%20flake). See

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