Gradle Task Configuration Avoidance

Hello Everyone, *If you are new to Beam and coming from non-Java language conventions, it is likely you are new to gradle. At the end of this email is a list of definitions and references to help understand this email.* *Short Version (For those who know gradle)*: A pull request [1] may fix the

Achievement unlocked: fully triaged

Hi all, I've finally done it! I've emptied the label "awaiting triage". Help me keep it that way! This ensures that we actually at least *look* at each issue once, preferably soon after it is filed. The idea is that you make sure the priority and other labels are right, since users are not

Re: Configuration Driven File Writes

Thanks for looking into this and the careful writeup. I've read the design doc and it looks great, but have a couple of questions. (1) Why did you decide on having a single top-level FileWrite transform whose config is ([common_parameters], [xml-params], [csv-params], ...) rather than separate

Configuration Driven File Writes

Hello Everyone, *For those new to Beam, even if this is your first day, consider yourselves a welcome contributor to this conversation. I remember what it was like first learning Beam on my own and I am passionate about everyone's learning experience. Below are definitions/references and a

Configuration driven Pub/Sub Writes

Hello Everyone, *For those new to Beam, even if this is your first day, consider yourselves a welcome contributor to this conversation. I remember what it was like first learning Beam on my own and I am passionate about everyone's learning experience. Below are definitions/references and a

Beam High Priority Issue Report (59)

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/24415 [Bug]: Cannot find