ronoaldo commented on issue #22931: URL: https://github.com/apache/beam/issues/22931#issuecomment-1244150828
I would also point out that the docs state this as being a possible workflow as of now, which is what confused me in the beginning: > 13.2.3. Using cross-language transforms in a Go pipeline > If a Go-specific wrapper for a cross-language is available, use that. Otherwise, you have to use the lower-level [CrossLanguage](https://pkg.go.dev/github.com/apache/beam/sdks/v2/go/pkg/beam#CrossLanguage) function to access the transform. > > Expansion Services > > The Go SDK supports automatically starting Java expansion services if an expansion address is not provided, although this is slower than providing a persistent expansion service. Many wrapped Java transforms manage perform this automatically; if you wish to do this manually, use the xlangx package’s [UseAutomatedJavaExpansionService()](https://pkg.go.dev/github.com/apache/beam/sdks/[email protected]/go/pkg/beam/core/runtime/xlangx#UseAutomatedJavaExpansionService) function. **In order to use Python cross-language transforms, you must manually start any necessary expansion services on your local machine and ensure they are accessible to your code during pipeline construction.** If 2.42 docs can be updated, it worth mentioning that calling Python from Go is unsupported, instead of telling that we must start the expansion service manually. -- 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]
