Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1911
Thanks @DrIgor for fix and explanation of the issue!
When RemoteInterpreterServer creates Interpreter, it [wraps interpreter
instance with
LazyOpenInterpreter](https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/remote/RemoteInterpreterServer.java#L187).
If we wrap interpreter instance with
[ClassLoaderInterpreter](https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/ClassloaderInterpreter.java)
as well, like [zeppelin do when creating interpreter
locally](https://github.com/apache/zeppelin/blob/ae1cb0527bc223b25761e1370618929e228183f8/zeppelin-zengine/src/main/java/org/apache/zeppelin/interpreter/InterpreterFactory.java#L1123),
then every interpreter will benefit by ClassloaderInterpreter.
ClassloaderInterpreter restores classloader after methods call.
@DrIgor @jongyoul Shell we try make RemoteInterpreterServer wrap
interpreter with ClassloaderInterpreter? what do you think?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
