Re: Portable Java Pipeline Support

I couldn't find any existing ticket for this issue (you may be the first to discover it). Feel free to create one with your findings. (FWIW I did find a ticket for documenting portable Java pipelines [1]). For the Flink and Spark runners, we run most of our Java tests using EMBEDDED mode. For port

Flaky test issue report

This is your daily summary of Beam's current flaky tests. These are P1 issues because they have a major negative impact on the community and make it hard to determine the quality of the software. BEAM-12200: SamzaStoreStateInternalsTest is flaky (https://issues.apache.org/jira/browse/BEAM-1

P1 issues report

This is your daily summary of Beam's current P1 issues, not including flaky tests. See https://beam.apache.org/contribute/jira-priorities/#p1-critical for the meaning and expectations around P1 issues. BEAM-12205: Dataflow pipelines broken NoSuchMethodError DoFnInvoker.invokeSetup() (https

Re: Portable Java Pipeline Support

Thank you, Kyle, for the detailed answer. Do we have a ticket track fix the LOOPBACK mode? LOOPBACK mode will be essential, especially for local testing as Samza Runner adopts portable mode and we are intended to run it with Java pipeline a lot. In addition, I noticed that this issue does not

Re: Portable Java Pipeline Support

Yes, we can expect to run java pipelines in portable mode. I'm guessing the method unimplemented exception is a bug, and we haven't caught it because (as far as I know) we don't test the Java loopback worker. As an alternative, you can try building the Java docker environment with "./gradlew :sdks

Portable Java Pipeline Support

Hi All, I am working on add portability support for Samza Runner and having been playing around on the support in Flink and Spark runner recently. One thing I noticed is the lack of documentation on how to run a java pipeline in a portable mode. Almost all document focuses on how to run a pyth

Re: Contributor Permission for Beam on Jira

Welcome! Love the Jira handle. Kenn On Fri, Apr 23, 2021 at 8:28 AM Jenny Xu wrote: > Thanks Alexey! > > Weiwen > > On Fri, Apr 23, 2021 at 11:24 AM Alexey Romanenko < > aromanenko@gmail.com> wrote: > >> Done. >> >> Welcome to Beam, Weiwen! >> >> --- >> Alexey >> >> On 23 Apr 2021, at 17:16

Re: Issues and PR names and descriptions (or should we change the contribution guide)

> On 22 Apr 2021, at 20:18, Robert Bradshaw wrote: > > On Thu, Apr 22, 2021 at 9:33 AM Kenneth Knowles > wrote: > Heuristic CI that says "this commit history looks OK" might solve a lot of > the problem (I see that Robert already started on this). > > And finally I wa

Re: Contributor Permission for Beam on Jira

Thanks Alexey! Weiwen On Fri, Apr 23, 2021 at 11:24 AM Alexey Romanenko wrote: > Done. > > Welcome to Beam, Weiwen! > > --- > Alexey > > On 23 Apr 2021, at 17:16, Jenny Xu wrote: > > Hi, > > This is Weiwen Xu. Could someone please add me as a contributor for Beam's > Jira issue tracker? My Jir

Re: Contributor Permission for Beam on Jira

Done. Welcome to Beam, Weiwen! --- Alexey > On 23 Apr 2021, at 17:16, Jenny Xu wrote: > > Hi, > > This is Weiwen Xu. Could someone please add me as a contributor for Beam's > Jira issue tracker? My Jira ID is JenX. > > Thanks, > Weiwen >

Contributor Permission for Beam on Jira

Hi, This is Weiwen Xu. Could someone please add me as a contributor for Beam's Jira issue tracker? My Jira ID is JenX. Thanks, Weiwen