Github user mridulm commented on the issue:
https://github.com/apache/spark/pull/17558
Just for clarity, this approach is broken - removal of jar will not cause
already loaded classes in jvm to be removed. Pursuing this approach is brittle
and will definitely break when classes from the jar have already been used :
causing runtime failures.
Proper resolution would be for appropriate classloader to be dropped and
new one created with the replaced jar (refer to how j2ee containers handle this
scenario for war files (for example)).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
