You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Java SDK timer tests fail, being unable to look up timers SDK side, even though the Go and Python SDKs don't seem to have this issue.
The error occurs in BeamFnDataInboundObserver.
error="bundle inst003 stage-004 failed:java.lang.IllegalStateException: Unable to find inbound timer receiver for instruction \"inst003\", transform \"first-ParMultiDo-Anonymous-\", and timer family \"\" No endpoint. Available keys: [ts-foo]\n\tat org.apache.beam.sdk.fn.data.BeamFnDataInboundObserver.multiplexElements(BeamFnDataInboundObserver.java:193 ...
So we do see that there is a timer there, so question is why does it look like Prism isn't actually populating the timer family being sent to the SDK.
I now have a quick fix for the root of the timer issue for Java. Need to validate that Python and Go continue to function as well.
But now the remaining test appears to have found a real bug in Prism! AFAICT this test will never terminate. org.apache.beam.sdk.transforms.ParDoTest\$TimerTests.testEventTimeTimerOrderingWithCreate
I'll need to statically read what the test is doing to see how it should terminate, so I can figure out what prism is doing wrong.
…r. (#32223)
* [#32221] Mark is-last for each timer stream correctly.
* Remove test override for clear, since it now passes unmodified.
* delint
---------
Co-authored-by: lostluck <[email protected]>
…rm pair. (apache#32223)
* [apache#32221] Mark is-last for each timer stream correctly.
* Remove test override for clear, since it now passes unmodified.
* delint
---------
Co-authored-by: lostluck <[email protected]>
Java SDK timer tests fail, being unable to look up timers SDK side, even though the Go and Python SDKs don't seem to have this issue.
The error occurs in BeamFnDataInboundObserver.
So we do see that there is a timer there, so question is why does it look like Prism isn't actually populating the timer family being sent to the SDK.
Full Suite iteration (two suites)
31 tests completed, 19 failed
7 tests completed, 6 failed
Going to iterate with the following to investigate.
TEST=org.apache.beam.sdk.transforms.ParDoTest\$TimerTests.testEventTimeTimerLoop
The text was updated successfully, but these errors were encountered: