bzhaoopenstack opened a new pull request, #20642:
URL: https://github.com/apache/flink/pull/20642

   Shade the fabric8 kubernetes deps with `org.apache.flink.shaded` prefix in 
flink-kubernetes
   
   ## What is the purpose of the change
   
   For supporting stepDecorators SPI(pluginable decorators), we propose to 
package the implementation class and associated dependencies into a plugin jar.
   So we need to load the said dependencies from parent class loader, as the 
most part / all of plugin decorators depend on the fabric8 kubernetes 
dependency, such as replies on the kubernetes models/client from fabric8.
   So we need to shade all the said classes in flink-kubernetes and flink-dist.
   
   
   ## Brief change log
   
   - Shade the `io.fabric.kubernetes` with `org.apache.flink.shaded` prefix.
   - Exclude the original left dependencies / classes / SPI files in flink-dist.
   
   
   ## Verifying this change
   
   Build the all flink packages, and verify the flink-kubernetes jar and 
flink-dist jar had re-leverage the affected dependecies, classes and files.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - 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): ( no)
     - 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)
   


-- 
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: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to