Gradle Build issue

Hi Devs, When I run the "Gradle build" command after I take the latest pull, I have been getting the following error. FAILURE: Build failed with an exception. * Where: *Build file '/home/vend/ApacheBeam/beam/buildSrc/build.gradle' line: 23* ** What went wrong:An exception occurred applying

Re: Contributor permission for Beam Jira tickets

Thank you Ahmet! From: Ahmet Altay Reply-To: "dev@beam.apache.org" Date: Tuesday, November 24, 2020 at 10:27 AM To: dev Subject: Re: Contributor permission for Beam Jira tickets Welcome. Added you as a contributor. On Tue, Nov 24, 2020 at 9:45 AM Alex Kosolapov

Contributor permissions for Beam Jira

Hi Beam, I am working at Samza Team at Linkedin and I would like to contribute to Samza Runner in Beam. My apache username is YC. Could I please have the permission to add/assign tickets on the Beam jira? Thanks, Yuhong

Re: Possible 80% reduction in overhead for flink runner, input needed

Agree this should be made the default (in the long term). There is no current plan to achieve this I'm aware of. I think we could get there by  a) first log a warning for pipelines without --fasterCopy about performance, that user should test his pipeline against DirectRunner (with mutability

Re: Contributor permission for Beam Jira tickets

Welcome. Added you as a contributor. On Tue, Nov 24, 2020 at 9:45 AM Alex Kosolapov wrote: > Hi! > > > > This is Alex from Akvelon. I working on examples for Beam, e.g, > https://lists.apache.org/thread.html/r332f7959cccbc8c5bc4166e698deac6ecd14b22b7af476f428ccbaf8%40%3Cdev.beam.apache.org%3E,

Re: Best way to resolve conflict between PipelineOption classes

Yes I think this renaming is OK. If you make awsRegion required, then existing pipelines will fail because it is missing. That is a feature - you can make the error message explain the change. In a perfect world we would also fix the mistake in the Dataflow options and have it be `gcpRegion` (or

Contributor permission for Beam Jira tickets

Hi! This is Alex from Akvelon. I working on examples for Beam, e.g, https://lists.apache.org/thread.html/r332f7959cccbc8c5bc4166e698deac6ecd14b22b7af476f428ccbaf8%40%3Cdev.beam.apache.org%3E,

Re: Possible 80% reduction in overhead for flink runner, input needed

Is there a plan/timeline to resolve the flag? It would be good for this to be the default, or only, behavior. The behavior with the flag activated is correct. It may still cause problems for users who accidentally depended on things outside the Beam model, so having a flag for them to opt-out

Re: Possible 80% reduction in overhead for flink runner, input needed

Hi Antonio, the PR is already merged [1]. It will be released as part of the upcoming 2.26.0 release [2]. You must activate the feature by using the --fasterCopy flag. Best,  Jan [1] https://github.com/apache/beam/pull/13240 [2] https://issues.apache.org/jira/browse/BEAM-11146 On