Thanks for checking it out @angoenka @tweise. I've checked out your code @tweise.
>From cursory test it seems error handling in the process launch needs some >fixing. The code actually fails if the binary path is not correct. It doesn't fail immediately when the process fails but it will time out. I'll introduce a check for the exit code when waiting for the connection from the SDK harness process. >We also need the ability to propagate the environment of the JVM plus set >additional environment variables to meet the contract of the Python worker. As things stand now, setting the correct environment variables is the responsibility of your startup script. But you're right, it doesn't make sense to pass the container contract parameters because the SDK harness processes rely on environment variables. Since we launch the process directly, we can set the required environment variables for the SDK harness. What do you want to achieve by propagating the environment of the JVM? [ Full content available at: https://github.com/apache/beam/pull/6287 ] This message was relayed via gitbox.apache.org for [email protected]
