Github user cfries commented on the issue:
https://github.com/apache/zeppelin/pull/2235
Hi Felix.
I am not sure if I got your point. The user can change CLASSPATH and
zeppelin.sh will use that. Also, the user can change
${ZEPPELIN_CLASSPATH_OVERRIDES} and ${ZEPPELIN_INTP_CLASSPATH_OVERRIDES} to add
additional files to the class path without changing CLASSPATH. I assume my
change is backward compatible. It is just that the script does not change the
CLASSPATH variable. But since the script is not supposed to call another
script, this should be OK.
In my option the side effect that the zeppelin.sh is polluting CLASSPATH
with the value of ZEPPELIN_CLASSPATH, which is then exported to interpreter.sh
is a bug, because it does not allow to use a JAR in zeppelin server which
should NOT be used in zeppelin interpreter. With my modification this is
possible.
Again: w.r.t. backward compatibility: I would assume that no one should
rely on the bug and if he relied on it, he can fix it by setting
ZEPPELIN_INTP_CLASSPATH_OVERRIDES or ZEPPELIN_INTP_CLASSPATH.
---
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.
---
