alpinegizmo commented on a change in pull request #9169: [FLINK-12998][docs] Update documentation for file systems loading as plugins URL: https://github.com/apache/flink/pull/9169#discussion_r307641027
########## File path: docs/monitoring/debugging_classloading.md ########## @@ -28,17 +28,20 @@ under the License. ## Overview of Classloading in Flink When running Flink applications, the JVM will load various classes over time. -These classes can be divided into two domains: +These classes can be divided into three groups based on their origin: - The **Java Classpath**: This is Java's common classpath, and it includes the JDK libraries, and all code - in Flink's `/lib` folder (the classes of Apache Flink and its core dependencies). + in Flink's `/lib` folder (the classes of Apache Flink and some dependencies). + + - The **Flink Plugin Components**: All code in folders under Flink's `/plugins` folder that loaded dynamically once via plugins mechanism during Flink's components start up. Review comment: I think this is trying to say that Flink's plugin mechanism will dynamically load all the code contained in folders under Flink's `/plugins` folder once during startup. ---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
