Hi Victor,
I'm facing the same issue, I'm working trying to re-enable some load tests
that use flink. My configuration in dataproc 2.0 and flink 1.12 as you.
I'll let you know if I found a solution for this issue, also if you find a
solution for this problem, please let me know how you solve it.
O
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.
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
High Priority Dependency Updates Of Beam Python SDK:
Dependency Name
Current Version
Latest Version
Release Date Of the Current Used Version
Release Date Of The Latest Release
JIRA Issue
cachetools
4.2.4
5.0.0
2021-12-27
ERROR: File 'src/.test-infra/jenkins/metrics_report/beam-metrics_report.html' does not exist
Agree that this might be an issue, though somewhat limited, because I
(strong emphasize) *suppose* that users skipping multiple releases do
care to test the upgrade appropriately. We can wait for more releases
between deprecating and removing the API. But I don't think adding a
different versio
