You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/01/02 10:19:03 UTC

[GitHub] [flink] wangyang0918 commented on issue #10678: [FLINK-15355][plugin] Remove parent first from plugin classloader.

wangyang0918 commented on issue #10678: [FLINK-15355][plugin] Remove parent first from plugin classloader.
URL: https://github.com/apache/flink/pull/10678#issuecomment-570166737
 
 
   Hi @pnowojski, i think we should use `parent loaded first` for user jars to avoid the class conflict and some fixed bugs of flink new version. However, for plugin jars, i do not think we need to do the same behavior. It will be better if we will delegate the `always-parent-first-pattern` configuration to each plugin implementation. Every plugin could decide which packages need to always load from parent.
   
   Otherwise, if we have two plugins and they have the different `always-parent-first-pattern`, we will have no idea how to deal with this.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services