yykaue opened a new pull request, #4517:
URL: https://github.com/apache/streampark/pull/4517

   ## What changes were proposed in this pull request
   
   Closes #4508.
   
   Fix Flink SQL application startup failures on Yarn Application and 
Kubernetes Application with Flink 2.x caused by missing runtime dependencies, 
conflicting shim classes, and logback configuration loading failures.
   
   Also fix Kubernetes Session REST health checks and increase cluster 
operation wait timeouts.
   
   ## Brief change log
   
   - Build per-application fat JARs for Yarn SQL jobs and preserve the 
generated artifact during submission.
   - Include snakeyaml in fat JARs, prioritize target-version shims during 
merging, and remove shims from Yarn `provided.lib.dirs`.
   - Load logback configuration through URL streams and preserve already shaded 
class names.
   - Bundle snakeyaml in Kubernetes SQL application images and handle missing 
Hadoop/Hive configuration directories.
   - Check Kubernetes Session clusters through the Flink REST API and increase 
deployment/shutdown wait timeouts from 60 to 300 seconds.
   
   ## Verifying this change
   
   - Added regression tests for logging configuration, shim merge order, SQL 
application packaging, Docker build contexts, Yarn submission artifacts, and 
Kubernetes Session health checks.
   - All 30 targeted regression tests passed.
   - Parameter compatibility checks passed with Flink 1.20.1, 2.0.2, and 2.2.1 
runtime JARs.
   - Spotless, Checkstyle, and Apache RAT checks passed.
   
   Startup and cancellation have not been verified against live Yarn/Kubernetes 
clusters.
   
   ## Does this pull request potentially affect one of the following parts
   
   - Dependencies (does it add or upgrade a dependency): No new Maven 
dependencies or version upgrades. The existing snakeyaml 2.0 dependency is 
bundled with SQL applications.


-- 
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]

Reply via email to