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

   ## Summary
   
   - Build and upload a per-application fat jar for **Yarn Application** Flink 
SQL jobs, pointing `flinkUserJar` at the app workspace artifact instead of the 
shared SqlClient jar.
   - Bundle **snakeyaml** into Yarn/K8s Application build pipelines so Flink 
SQL YAML parsing works in container images.
   - Add **`FlinkParameterToolBridge`** so SqlClient resolves `ParameterTool` 
across Flink 1.x (`org.apache.flink.api.java.utils`) and Flink 2.x 
(`org.apache.flink.util`) package relocations.
   - Fix **`StreamParkLoggerFactory`** to load logback XML from classpath URL 
streams and rewrite shaded class names, avoiding file-path failures under 
parent-first classloading on K8s Application mode.
   - Introduce **`ShimJarMergeOrder`** and update **`MavenTool`** so Flink 2.x 
shims win over 1.x entries when merging fat jars.
   - Stop adding shims artifacts to Yarn Application **`provided.lib.dirs`** in 
`YarnApplicationClient`.
   - Treat **Kubernetes Session** clusters as HTTP-remotable in 
`FlinkClusterWatcher` for REST health checks.
   - Increase Kubernetes session cluster deploy/shutdown timeout from 60s to 
300s for slow cluster startup.
   
   Closes #4508.
   
   ## Test plan
   
   - [x] Verified `FlinkSQL200OnYarnTest` (Flink 2.0.2 Yarn Application + 
Session) locally — 10/10 passed
   - [ ] Manual: create/release/start/cancel a Flink SQL app on Yarn 
Application mode with Flink 2.x
   - [ ] Manual: create/release/start/cancel a Flink SQL app on Kubernetes 
Application mode with Flink 2.x
   - [ ] `./mvnw -pl 
streampark-flink/streampark-flink-sqlclient,streampark-flink/streampark-flink-packer
 -am test -DskipTests` (compile)
   
   
   Made with [Cursor](https://cursor.com)


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