This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/30266 [Bug]: Cannot read
Please review the release of the following artifacts that we vendor,
following the process [5]:
* beam-vendor-grpc-1-60-1:0.2
Hi everyone,
Please review and vote on the release candidate #1 for the version
beam-vendor-grpc-1-60-1:0.2 as follows:
[ ] +1, Approve the release
[ ] -1, Do not appr
+1.
Checked postcommit test results for Python SDK, and exercised a couple of
Datadow scenarios.
On Thu, Feb 8, 2024, 14:07 Svetak Sundhar via dev
wrote:
> +1 (Non-Binding)
>
> Tested with Python SDK on DirectRunner and Dataflow Runner
>
>
> Svetak Sundhar
>
> Data Engineer
> s vetaksund...@g
Also tested with GCP IO performance benchmark [1]. Passed other than
SpannerIO where the benchmark failed due to issues in the test suite itself
[2], not related to Beam.
+1 but I had voted for another validation suite before for this RC
[1]
https://github.com/GoogleCloudPlatform/DataflowTemplate
I validated that the release artifacts are all correct, tested some simple
Python and Yaml pipelines. Everything is looking good so far.
However, could I ask that you hold this vote open a little longer? We've
got some Dataflow service side changes that relate to 2.54 being the first
release where
I can agree to that Robert Bradshaw. Thank you for letting the community know.
(Disclaimer: I am on the Dataflow team myself, but do try to keep my hats
separated when I'm release manager).
It would be bad for Beam users who use Dataflow to try to use the release but
be unaware of the switch. I
