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
I think the goals are good:
- be able to release fixes quicker
- have users discover PubsubLiteIO
Just to clarify a little - a user currently has to depend on (probably)
org.apache.beam:beam-sdks-java-core,
org.apache.beam:beam-runners-direct-java,
Thanks for noticing that! The key was updated prior to signature. I need a
PMC member's help to copy the new keys to the release folder:
svn cp https://dist.apache.org/repos/dist/dev/beam/KEYS
https://dist.apache.org/repos/dist/
release/beam/KEYS
On Fri, Jul 2, 2021 at 9:27 AM Robert Bradshaw
I'm not sure what is the conclusion here. I'd suggest the following:
a) merge fix for BEAM-12538 ([1]), so that it can be fixed in 2.32.0,
because the current state is not good
b) make a decision about whether to send expansion options via
ExpansionRequest, or not
c) in either case, we
