[BEAM-735] PAssertStreaming should make sure the assertion happened.

• Type: Bug
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Fix Version/s: 0.3.0-incubating
• Component/s: runner-spark
• Assignee: Amit Sela
• Reporter: Amit Sela
• Created: 09/Oct/16 14:24
• Updated: 16/May/20 13:46
• Resolved: 14/Oct/16 14:13

Description

The Spark runner currently runs PAsserts via `PAssertStreaming` which groups into a single key and asserts the values on the worker (part of the "Lambda" in the Spark lingo).
This could be a problem since Spark won't run if there's nothing to process - so that if for some reason the input is missed, say reading from Kafka latest or simply an empty topic, the assertion will be skipped and so we'll never fail (we would like to fail if there was no input, while we expected one).

This might change once Spark provide a better support for the Beam model in streaming, but until then, it's best that our tests will consider this case as well.

I'll add an aggregator and increment for assertion, at the end I'll make sure the aggregator is not 0, so that at least one assertion took place (if for some reason Spark kept on for a couple of more intervals it might execute the same assertion more then once, if the input is repeated).

Issue Links

• links to: GitHub Pull Request #1073