Re: Chronically flaky tests

I like: *Include ignored or quarantined tests in the release notes* *Run flaky tests only in postcommit* (related? *Separate flaky tests into quarantine job*) *Require link to Jira to rerun a test* I am concerned about: *Add Gradle or Jenkins plugin to retry flaky tests* - because it is a

Re: [DISCUSS] How many Python 3.x minor versions should Beam Python SDK aim to support concurrently?

We have added Python 3.8 support in Apache Beam 2.23.0 release[1] and established the plan to remove Python 2.7 support in 2.25.0 release[2]. I think it is in the interest of the community to reduce the overhead associated with adding and removing support of Python minor versions in Beam in the

Broken links in code velocity dashboard

Currently the open PRs section of the dashboard [1] seems to be broken. PRs are linking to https://github.com/damgadbot/beam/issues/ instead of https://github.com/apache/beam/pull/. And the PR list showing PRs from the (https://github.com/damgadbot/beam) fork in addition to the main repo.

[PROPOSAL] Making ParquetIO Splittable

Hi everyone, I am working on a project that enables the splittable reading for ParquetIO.The JIRA issue is here and I have created a PR for the issue. I have also attached my design doc

Request Throttling in OSSIO

Hello Dev team, We are giving our first shot in writing Beam IO connector for Oracle Streaming Service (OSS). The plan is to first implement it for enterprise use and based on the feedback and stability make it available open source. This is our first attempt in developing a Beam IO connector and

Re: [ANNOUNCE] Beam 2.23.0 Released

Hi Valentyn, Thanks for the information! I am trying to see what Flink version does Beam 2.23.0 support, but the information is not available here https://beam.apache.org/documentation/runners/flink/. Can you please clarify? Thanks a lot! Eleanore On Wed, Jul 29, 2020 at 5:47 PM Valentyn

Re: [ANNOUNCE] Beam 2.23.0 Released

Hi Eleanore, there have been no changes to Beam's supported Flink versions since Beam 2.21.0. Beam supports Flink 1.8, 1.9, and 1.10. If you are looking for Flink 1.11 support, I didn't find an existing issue, so I filed https://issues.apache.org/jira/browse/BEAM-10612. On Thu, Jul 30, 2020 at

Re: Making reporting bugs/feature request easier

On Wed, Jul 29, 2020 at 7:12 PM Kenneth Knowles wrote: > > On Wed, Jul 29, 2020 at 11:08 AM Robert Bradshaw > wrote: > >> +1 to a simple link that fills in most of the fields in JIRA, though this >> doesn't solve the issue of having to sign up just to submit a bug report. >> Just using the

[RESULT][VOTE] Make Apache Beam 2.24.0 the final release supporting Python 2.

This vote has passed with 9 approving +1 votes, 5 of which belong to Apache Beam PMC. We will announce Apache Beam 2.24.0 as the final release with Python 2 support and prepare to remove Python 2 support in Apache Beam 2.25.0. Thanks, Valentyn

Re: [VOTE] Make Apache Beam 2.24.0 the final release supporting Python 2.

I also vote +1 and close this vote. On Mon, Jul 27, 2020 at 9:46 AM Ismaël Mejía wrote: > +1 > > On Fri, Jul 24, 2020 at 10:49 PM Udi Meiri wrote: > > > > +1 > > > > On Fri, Jul 24, 2020 at 10:47 AM Maximilian Michels > wrote: > >> > >> +1 > >> > >> On 24.07.20 18:54, Pablo Estrada wrote: >

Re: Email about build runs on my fork.

You can disable GitHub actions on your own repos via the UI or via a code change https://github.community/t/how-can-i-disable-a-github-action/17049 On Thu, Jul 30, 2020, 12:15 PM Ahmet Altay wrote: > /cc +tobiasz.kedzier...@polidea.com +Emily > Ye -- this question is related to one of the

Re: Email about build runs on my fork.

/cc +tobiasz.kedzier...@polidea.com +Emily Ye -- this question is related to one of the recent github action prs. On Thu, Jul 30, 2020 at 10:23 AM Alex Amato wrote: > Hi, > > I received this email indicating some build was running on my fork, though > I had not been doing any work on that

Email about build runs on my fork.

Hi, I received this email indicating some build was running on my fork, though I had not been doing any work on that fork for the last few weeks. I don't really need to run these builds on my fork and don't think we need to waste resources on this. Is there some way to prevent forks from doing

Re: Making reporting bugs/feature request easier

On Thu, Jul 30, 2020 at 6:37 AM Maximilian Michels wrote: > +1 for making it easier to report bug. Very often we have users report a > bug and then they have to rely on a developer to report the issue > because they don't want to bother creating a JIRA account (which is > understandable). If you

Beam Summit Status Report - 7/29

Hi folks, I wanted to provide you with the Beam Summit Status report from yesterday's meeting. If you would like to join the next public meeting on Wednesday, August 5th at 11:30 AM PST please let me know and I will send a calendar invite over to you! Also don't forget to register for the Summit

Re: Making reporting bugs/feature request easier

+1 for making it easier to report bug. Very often we have users report a bug and then they have to rely on a developer to report the issue because they don't want to bother creating a JIRA account (which is understandable). If you have a JIRA account it is easy because you don't need any

[GitHub] [beam-site] tvalentyn merged pull request #605: Publish 2.23.0 release

tvalentyn merged pull request #605: URL: https://github.com/apache/beam-site/pull/605 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