StefanRRichter opened a new pull request #8038: [FLINK-11953] Introduce 
Plugin/Loading system and integrate it with FileSystem
URL: https://github.com/apache/flink/pull/8038
 
 
   ## What is the purpose of the change
   
   We want to change the general architecture for loading FileSystems in Flink 
to a plugin architecture. The advantage of this change is that it would invert 
the classloading from parent-first to child-first and therefore enables us to 
move away from shading to avoid class/version conflics.
   
   Note that this general approach could also be used in other places for Flink 
in the future, but this task is targetting only the file systems for now. 
Furthermore, this is the first PR, introducing the general mechanism. We still 
need followup work with changes to the build and shipping/providing the plugin 
folder.
   
   ## Brief change log
   - Made {{ChildFirstClassLoader}} a toplevel class.and move to flink core.
   - Introduce {{Plugin}} interface, {{PluginLoader}}, {{PluginManager}} for 
basic plugin mechanism.
   - Introduce init of plugin manager singleton to process entry points.
   - Integrate plugin mechanism with {{FileSystem}} class.
   
   ## Verifying this change
   
   Added unit tests.
   
   ## 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)`: (yes)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
     - The S3 file system connector: (yes)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes)
     - If yes, how is the feature documented? (feature not yet compelted)
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to