lostluck opened a new issue, #27038: URL: https://github.com/apache/beam/issues/27038
### What happened? Because the Setup context is uncached (https://github.com/apache/beam/blob/833261f0a041e04ca4dcb8719424fda09edcc5e6/sdks/go/pkg/beam/core/runtime/exec/pardo.go#L104) metrics initialized in Setup are lost, which is unexpected. Work done in setup, while logically outside of a bundle, will be under the context of the first bundle to execute that transform. So there needs to be a way to transfer/extract the metrics from the Setup context so they are recorded back to the runner. ### Issue Priority Priority: 3 (minor) ### Issue Components - [ ] Component: Python SDK - [ ] Component: Java SDK - [X] 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 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
