zentol edited a comment on pull request #17521: URL: https://github.com/apache/flink/pull/17521#issuecomment-953802124
But the user-jar is the same for all tasks. You can't use a manifest in said jar for differentiating which classes should now be loaded / made accessible. You either a) need the CL factory to create a task-specific classloader (which you can't because jars are the same and CLs are shared) or b) need the cooperation from the user-code to load classes in a specific way. We are painfully aware of the dependency conflicts between connectors; there are some ideas floating around to make connectors themselves work as plugins such that they each have their own classloader, but I'm not sure where exactly we are at on that front. I think we'd rather focus on that than introducing a separate mechanism for effectively the same use-case that would also be more difficult to use. -- 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
