Hi everyone,
Please review and vote on the release candidate #1 for the version 2.31.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
Reviewers are encouraged to test their own use cases with the release
candidate, and vote +1 if no
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
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
Update for anyone who might run into this:
I was able to get this fixed by using beam.io.ReadAllFromAvro([input]) instead
of beam.io.ReadFromAvro(input).
After some digging I realized that `ReadFromAvro` relies on splittable
dofns to split reads and splittable do fns are not supported in
Hi team,
This is Marco and I would like to be added to the Apache Beam contributor
list, my username is 'marroble'.
Thanks!
--
*This email and its contents (including any attachments) are being sent to
you on the condition of confidentiality and may be protected by legal
privilege. Access to
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
chromedriver-binary
91.0.4472.101.0
Hi Cham, thanks for the feedback
> Beam has a policy of no knobs (or keeping knobs minimum) to allow runners
to optimize better. I think one concern might be that the addition of this
option might be going against this.
I agree that less knobs is more. But if assignment of a key is specific per
