sangkyoonnam opened a new pull request, #29503: URL: https://github.com/apache/flink/pull/29503
## What is the purpose of the change Bump pemja to 0.5.8 for [FLINK-38500](https://issues.apache.org/jira/browse/FLINK-38500), including the JDK 17 `NoSuchFieldException: loadedLibraryNames` fix ([alibaba/pemja#100](https://github.com/alibaba/pemja/pull/100)). ## Brief change log - Bump `com.alibaba:pemja` to 0.5.8 in `flink-python/pom.xml` and `NOTICE`, and the Python requirement in `setup.py` and `pyproject.toml` ## Verifying this change I didn't build release-2.3. On macOS arm64, I replaced the bundled pemja classes in `flink-python-2.3.0.jar` with the 0.5.8 classes and used Python pemja 0.5.8. The FLINK-38500 reproducer passes all three consecutive thread-mode submissions to one session cluster on both JDK 11 and 17. With the stock jar and pemja 0.5.7, submissions 2 and 3 fail on JDK 17. The replacement `pemja/` classes match those in the tested release-2.2 and release-1.20 builds byte-for-byte. No new automated test was added. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): yes - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no - The serializers: no - The runtime per-record code paths (performance sensitive): yes, pemja's Java/Python value conversion (alibaba/pemja#101, alibaba/pemja#102); no Flink runtime code changes - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no - If yes, how is the feature documented? not applicable --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (please specify the tool below) AI was used for the verification runs and this description. Generated-by: Claude Code 2.1.302 (Claude Opus 5.5) -- 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]
