P1 issues report (78)

2022-05-11 Thread Beam Jira Bot
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 https://beam.apache.

Flaky test issue report (56)

2022-05-11 Thread Beam Jira Bot
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 determin

Plugging in a new backend

2022-05-11 Thread Tony Wang
Hello, I am a PhD student at Stanford working on a new data processing backend, similar to Spark/Flink: https://github.com/marsupialtail/quokka I am wondering how feasible it is to plug it in as a backend for Apache Beam, i.e. is it even supported, how much work would it be? Best, Tony

Re: Plugging in a new backend

2022-05-11 Thread Robert Burke
I believe we have a page for that: https://beam.apache.org/contribute/runner-guide/ Likely easiest if you're using Java, more to crib from. But as long as the language speaks GRPC it's feasible. On Wed, May 11, 2022, 10:30 AM Tony Wang wrote: > Hello, > > I am a PhD student at Stanford working

Re: Plugging in a new backend

2022-05-11 Thread Robert Burke
Given we're well into Portability First, we may want to put all the Portable Stuff at the top of the document these days and clearly mark the Legacy approaches as such. On Wed, May 11, 2022, 10:42 AM Robert Bradshaw wrote: > Yes, Beam at its core is designed to have plugable runners. Since I > s

Changing the interface in CassandraIO Mapper

2022-05-11 Thread Vincent Marquez
I would like to do some additional performance related changes to the CassandraIO module, but it would necessitate changing the Mapper interface to return ListenableFuture opposed to java.util.concurrent.Future. I'm not sure why the Mapper interface specifies the former, as the datastax driver its

Re: Changing the interface in CassandraIO Mapper

2022-05-11 Thread Vincent Marquez
On Wed, May 11, 2022 at 3:12 PM Daniel Collins wrote: > ListenableFuture has the additional problem that beam shades guava, so its > very unlikely you would be able to put it into the public interface. > > I'm not sure why this would be the case, there are other places that make use of Listenable