[
https://issues.apache.org/jira/browse/BEAM-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles updated BEAM-10444:
-----------------------------------
Resolution: Fixed
Status: Resolved (was: Resolved)
Hello! Due to a bug in our Jira configuration, this issue had status:Resolved
but resolution:Unresolved.
I am bulk editing these issues to have resolution:Fixed
If a different resolution is appropriate, please change it. To do this, click
the "Resolve" button (you can do this even for closed issues) and set the
Resolution field to the right value.
> Simpler PAssert for simpler cases
> ---------------------------------
>
> Key: BEAM-10444
> URL: https://issues.apache.org/jira/browse/BEAM-10444
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Robert Bradshaw
> Assignee: Robert Bradshaw
> Priority: P2
> Labels: Done, stale-assigned
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The existing PAssert uses non-trivial triggers, custom java WindowFns, and a
> complicated structure to be able to correctly validate even the most complex
> scenarios. This makes it more difficult to debug and harder to use validates
> runner tests when bootstrapping runner implementations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)