+1
Probably worth to check if we have dependencies that rely on Byte
Buddy that can produce conflicts but I doubt it.
My only worry was ASM leaking into the classpath, but it seems that
Byte Buddy already shades ASM so that should not be an issue.
Ismaël
On Thu, Mar 17, 2022 at 5:09 PM Liam Mil
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
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.
Hi community,
We are working on the new Apache CDAP IO connector. So could anyone please add
us to the GCP project apache-beam-testing to be able to test our Beam pipelines
there with the Dataflow runner?
email addresses of the development team:
igor.krasa...@akvelon.com
vitaly.terent...@akvel
Hey all
I'm trying to run an Apache Beam pipeline on Flink (hosted on GKE). I'm
using a custom container image that was built to run trained TensorFlow
models on a series of images, but the base Docker image is
apache/beam_python3.7_sdk:2.30.0, with a few libraries installed on top of
that.
I'm
Apologies to Danny, i haven't read your considered reply yet, as i need to
address Kerry's question on priorities immediately.
I feel it's entirely critical to have before native streaming, because it
serves users more in the long term.
The cost of waiting is that we can't establish the convent