ZEPPELIN-546 Enables interpreter library loading from maven repository#590
ZEPPELIN-546 Enables interpreter library loading from maven repository#590minahlee wants to merge 5 commits intoapache:masterfrom
Conversation
|
Looks great! A quick question if it's ready to merge: Also, is there a reason not to handle documentation update in the same PR as feature and it's tests? |
|
@bzz Thanks for review. Dependencies that added to |
|
@minahlee still doesn't make much sense to separate the docs into a different PR. |
8b1f240 to
2af3bea
Compare
|
I think how to split large work into small peices of PRs is up to contributors. (although smaller PR helps review process) |
|
@Leemoonsoo Yes, it will be better to have both at the same time to merge them together. |
|
@minahlee @AhyoungRyu - thanks for explanations, makes perfect sense to have 2 PRs for 2 ppl! Looks good to me. |
|
LGTM!! It also makes any kind of jars loaded easily. I could load JDBC libraries using this feature. |
- Move org.apache.zeppelin.spark.dep package from zeppelin-spark to zeppelin-interpreter - Rename DependencyResolver/DependencyContext to SparkDependencyResolver/SparkDependencyContext - Add general DependencyResolver
39ecf9d to
72ad12c
Compare
|
Rebased master branch and CI build passed |
|
Great. LGTM |
…m maven repository ### What is this PR for? This PR is related to #590. This documentation may explain the overall process of **Dynamic Interpreter Loading** in [Helium Proposal](https://issues.apache.org/jira/browse/ZEPPELIN-533). Moreover, at the last this documentation, Zeppelin users can get the basic information about step by step of interpreter setting & configuring & binding. Since I assumed that they are novice at Zeppelin. ### What type of PR is it? Documentation ### Todos * [x] - Add docs image under `/docs/assets/themes/zeppelin/img/docs-img/` * [x] - Add dynamicinterpreter.md * [x] - Add dynamicinterpreter.html location to `docs/_includes/themes/zeppelin/_navigation.html` ### Is there a relevant Jira issue? 1. [ZEPPELIN-533 Helium](https://issues.apache.org/jira/browse/ZEPPELIN-533) 2. [ZEPPELIN-546](https://issues.apache.org/jira/browse/ZEPPELIN-546) ### How should this be tested? I add a link of this documentation to `interpreter tab` in Zeppelin web page.  ### Screenshots (if appropriate) Hopefully, below image helps you to understand this process : )  ### Questions: * Does the licenses files need update? No. * Is there breaking changes for older versions? No. * Does this needs documentation? No. Author: Ryu Ah young <[email protected]> Closes #609 from AhyoungRyu/ZEPPELIN-546-docs and squashes the following commits: d0675e0 [Ryu Ah young] ZEPPELIN-546-docs: Fix some sentences 266dac0 [Ryu Ah young] ZEPPELIN-546-docs: Add content for licence e180a8e [Ryu Ah young] ZEPPELIN-546-docs: Fix typo again d3cc50f [Ryu Ah young] ZEPPELIN-546-docs: Fix typo a9ec7d7 [Ryu Ah young] ZEPPELIN-546-docs: Add dynamicinterpreterload.html location to _navigation.html 16b46f4 [Ryu Ah young] ZEPPELIN-546-docs: Add dynamicinterpreterload.md 3067025 [Ryu Ah young] ZEPPELIN-546-docs: Add docs image
| Logger logger = LoggerFactory.getLogger(DependencyResolver.class); | ||
|
|
||
| private final String[] exclusions = new String[] {"org.apache.zeppelin:zeppelin-zengine", | ||
| "org.apache.zeppelin:zeppelin-interpreter", |
There was a problem hiding this comment.
hi, was there any reason to not include all the exclusions mentioned in SparkDependencyResolver.java here?
"org.scala-lang:scala-library","org.scala-lang:scala-compiler","org.scala-lang:scala-reflect","org.scala-lang:scalap" - these are present in the exclusions in SparkDependencyResolver.java but not here.
There was a problem hiding this comment.
AFAIK, spark already has scala related packages but this doesn't have them.
What is this PR for?
This PR enables library loading from maven repository to load interpreter binaries.
To leverage current spark interpreter's library loading, moved org.apache.zeppelin.spark.dep(under spark) to org.apache.zeppelin.dep(under zeppelin-interpreter).
Making REST API and loading interpreter property on runtime will be the next step to complete ZEPPELIN-546 and will be handled in different PR.
What type of PR is it?
Feature
Is there a relevant Jira issue?
ZEPPELIN-546
Questions:
zeppelin-interpreter/pom.xmlis already used in other module)