Github user radekg commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/386#issuecomment-153572008
@Leemoonsoo: I think not exactly. `ZEPPELIN_CLASSPATH` is built by
prepending elements to the classpath, meaning, whatever the user puts in the
class path is, at the time of complete class path, placed at the very end of
the class path. Consider a scenario:
Somebody wants to put a patched `spark-core` jar into the class path. He
will set `ZEPPELIN_CLASSPATH` to his `/opt/whatever/spark-core_2.10-1.5.1.jar`
and proceed with the standard procedure for `zeppelin.sh`. His jar will not be
the effective one. The reason is that the class path built by Zeppelin is the
following:
ZEPPELIN_CLASSPATH=<addJar>:$ZEPPELIN_CLASSPATH
...
ZEPPELIN_CLASSPATH=<addJar>:$ZEPPELIN_CLASSPATH
I believe what @echarles introduces here, is the mechanism for the user to
be able to override any arbitrary functionality _no matter what_.
Very nice feature, @echarles.
---
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.
---
