[jira] [Commented] (BEAM-1763) TestPipeline should ensure that all assertions succeeded

["Pei He (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16146547#comment-16146547 ] 

Pei He commented on BEAM-1763:
------------------------------

Do we require runners to quiesce when bounded data was processed?

Otherwise, runner that supports metrics but doesn't quiesce (run in streaming mode) still cannot use TestPipeline.

> TestPipeline should ensure that all assertions succeeded
> --------------------------------------------------------
>
>                 Key: BEAM-1763
>                 URL: https://issues.apache.org/jira/browse/BEAM-1763
>             Project: Beam
>          Issue Type: Sub-task
>          Components: sdk-java-core
>            Reporter: Thomas Groh
>            Assignee: Aviem Zur
>             Fix For: 2.0.0
>
>
> This doesn't need to be part of each {{PipelineRunner}} implementation if it goes through the {{PipelineResult}} APIs. The assertion can be of the form that if the Pipeline is finished, then the number of successful assertions is equal to the total number of assertions.
> Suggested solution:
> For runners which support metrics, use the counters for successful/failed assertions and compare them to expected number of assertions.
> Runners which do not support metrics should either implement metrics or override {{PAssert}} in a way that verifies its execution.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)