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
Run the TestXlang_CoGroupBy test from the Go validates runner suite.
Data gets corrupted, and if the Go SDK does loopback execution the passert returns the following:
actual PCollection does not match expected values
=========
0 correct entries (present in both)
=========
2 unexpected entries (present in actual, missing in expected)
+++
1964988:[]
+++
1:[]
=========
2 missing entries (missing in actual, present in expected)
---
0:[1 2 4]
---
1:[3 5 6]
As this is only happening in prism (other runners seem to cope), either prism's unfused execution is causing corruption on the Java side, OR it's prism receiving it is causing the corruption. Either way, it needs to be fixed so the pipeline passes.
Fusion was added in #29306 which is currently enabled by default. It's most likely that fusion will be enabled by default for xlang based pipelines anyway (if not for non-go pipelines). This issue can be closed once the CoGBK test is no longer filtered out.
What happened?
Run the TestXlang_CoGroupBy test from the Go validates runner suite.
Data gets corrupted, and if the Go SDK does loopback execution the passert returns the following:
As this is only happening in prism (other runners seem to cope), either prism's unfused execution is causing corruption on the Java side, OR it's prism receiving it is causing the corruption. Either way, it needs to be fixed so the pipeline passes.
The test in question is here:
beam/sdks/go/test/integration/xlang/xlang_test.go
Line 134 in 228157f
It needs to be unfilered from the prism run here though:
beam/sdks/go/test/integration/integration.go
Line 143 in 228157f
The following action workflow runs the suite:
https://github.com/apache/beam/actions/workflows/beam_PreCommit_GoPrism.yml
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components
The text was updated successfully, but these errors were encountered: