peterphitran commented on PR #39064: URL: https://github.com/apache/beam/pull/39064#issuecomment-4880740787
Yeah, that matches what I found. Confirmed the jar is Java 17 and it's launched on the runner's Java 11, so ServiceLoader hits the Iceberg registrar and the service fails to start. I tested it locally, the jar fails on JDK 11 and starts cleanly on JDK 17. The path in the log is $JAVA_HOME/bin/java, so subprocess_server takes the JVM from JAVA_HOME. On why it's still Java 11, I believe the -PtestJavaVersion=17 we added isn't activating because these are pull_request_target workflows, so CI runs master's YAML, not the PR's. If that's right, the flag only takes effect after merge, which is why the run still shows Java 11. Worth flagging: since Iceberg is bundled in the shared io expansion-service jar, that jar is effectively Java-17-only at runtime for any Managed transform, not just Iceberg. beam_PerformanceTests_xlang_KafkaIO_Python still defaults to Java 11, so it's likely exposed too. -- 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]
