Feedback for documentation on Testing Beam pipeline
The documentation is not at all detailed and is pretty shallow, hardly covering
most concepts to effectively design test-suit for an enterprise level pipeline.
For example, some the missing information are –
1. How to test the pipeline when
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.
I have a PR to make the proposed change
https://github.com/apache/beam/pull/15201
Apache Legal says the approach seems fine as well:
https://issues.apache.org/jira/browse/LEGAL-582
So this is likely going to be merged in today, and possibly cherry picked into
the freshly cut release to get the
One more note - the PR has a bunch of failing tests, which I plan to
fix, once there is a consensus, that the overall approach is the correct
one.
Thanks,
Jan
On 7/22/21 7:20 PM, Jan Lukavský wrote:
Hi,
this was a ride. But I managed to get that working. I'd like to
discuss two points, t
