Re: [I] [Bug]: Difficult to use Portable Flink Runner with Go [beam]

["lostluck (via GitHub)" <gi...@apache.org>]

lostluck commented on issue #26485:
URL: https://github.com/apache/beam/issues/26485#issuecomment-2590784945

   Apologies for not engaging with this previously, but I was pinged directly recently, so I've started to look into it, and this is the "best" existing bug for tracking the overall work.
   
   I've just merged in `--worker_pool` support for the Go SDK in #33572 to be part of the 2.63 release. This enables running a SideCar External Worker container for the Go SDK, as per the previously linked Java Documentation.
   
   The other blocker is the javaless "uberjar" support, mentioned in #21234 to more easily submit to Flink. That work will be better described, and ultimately tracked there.
   
   Poor documentation is also mentioned in #20424 
   
   Overall, I would like it to be possible for any portable SDK to be able to submit to Flink without re-implementing the wheel. 
   
   The minimum end goal is to allow the Go SDK to run at least as well as described for the Python SDK here: https://beam.apache.org/blog/deploy-python-pipeline-on-flink-runner/ (which is itself not great), but the SDK will at least be at parity.


-- 
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: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org