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
When attempting to run the Swift SDK wordcount, prism failed due to a missing base coder, but ultimately there was no coder id. However, each transform and PCollection had appropriate coders.
Aside from resolving the root cause triggering the issue, prism should provide appropriate context for that error instead of lazily panicking. This requires plumbing errors all the way back up, allowing clarity in the error message for what prism was doing at the time.
Issue Priority
Priority: 3 (minor)
Issue Components
Component: Python SDK
Component: Java SDK
Component: Go SDK
Component: Typescript SDK
Component: IO connector
Component: Beam examples
Component: Beam playground
Component: Beam katas
Component: Website
Component: Spark Runner
Component: Flink Runner
Component: Samza Runner
Component: Twister2 Runner
Component: Hazelcast Jet Runner
Component: Google Cloud Dataflow Runner
The text was updated successfully, but these errors were encountered:
* [#28126] plumb coder errors with better context.
* Add hard clear checks for SDK error: no windows being encoded.
* parse log
* fix log line parsing
* fmt
---------
Co-authored-by: lostluck <[email protected]>
* [apache#28126] plumb coder errors with better context.
* Add hard clear checks for SDK error: no windows being encoded.
* parse log
* fix log line parsing
* fmt
---------
Co-authored-by: lostluck <[email protected]>
What happened?
When attempting to run the Swift SDK wordcount, prism failed due to a missing base coder, but ultimately there was no coder id. However, each transform and PCollection had appropriate coders.
Aside from resolving the root cause triggering the issue, prism should provide appropriate context for that error instead of lazily panicking. This requires plumbing errors all the way back up, allowing clarity in the error message for what prism was doing at the time.
Issue Priority
Priority: 3 (minor)
Issue Components
The text was updated successfully, but these errors were encountered: