[Feature Request]: Provide error log for troubleshooting newJarGetter function
What would you like to happen?
I tried to run Dataflow Job in k8s job. I received the following error
goroutine 1 [running]:
github.com/apache/beam/sdks/v2/go/pkg/beam/core/runtime/xlangx/expansionx.newJarGetter()
/go/pkg/mod/github.com/apache/beam/sdks/[email protected]/go/pkg/beam/core/runtime/xlangx/expansionx/download.go:56 +0x23
github.com/apache/beam/sdks/v2/go/pkg/beam/core/runtime/xlangx/expansionx.init()
/go/pkg/mod/github.com/apache/beam/sdks/[email protected]/go/pkg/beam/core/runtime/xlangx/expansionx/download.go:45 +0xf
The error returned by the user.Current() method is ignored, it hards for me to debug the issue https://github.com/apache/beam/blob/e68a79c03f4a059da7d62d5d1cc16e7c5c3ee504/sdks/go/pkg/beam/core/runtime/xlangx/expansionx/download.go#L55
I wish we could check the error message for troubleshooting.
Issue Priority
Priority: 2 (default / most feature requests should be filed as P2)
Issue Components
- [ ] Component: Python SDK
- [ ] Component: Java SDK
- [X] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam YAML
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Infrastructure
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
I just left a comment on https://github.com/apache/beam/issues/23647 with what I found to be a workaround. But I agree that there should be more helpful logging!
This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.
This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.