Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1831
**For reviewers**
Fixed to use `spark.jars` instead of `classpath`.
- classpath doesn't include submitted jars at this moment (i could get 7
days ago, but not now)
- it enable to simplify logic since we don't need to get classpath before
setting new classpath. In other words, we can directly set PYTHONPATH in
`setupPySparkEnv` function.
- Also tested in spark 1.6.2, spark 2.0.0
@zjffdu
The spark code we talked came from
https://github.com/apache/spark/pull/6360. It seems like intended so it's ok
not to raise an issue.
---
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.
---
