You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Christian Tzolov (JIRA)" <ji...@apache.org> on 2015/08/24 11:40:45 UTC
[jira] [Created] (ZEPPELIN-259) Generalize the Dependency
implementation
Christian Tzolov created ZEPPELIN-259:
-----------------------------------------
Summary: Generalize the Dependency implementation
Key: ZEPPELIN-259
URL: https://issues.apache.org/jira/browse/ZEPPELIN-259
Project: Zeppelin
Issue Type: Improvement
Components: Core, Interpreters
Affects Versions: 0.6.0
Reporter: Christian Tzolov
Currently the *DepInterpreter* (%dep) is bound to the Spark group only.
It will be beneficial for many other interpreters and use cases if the dependency functionality is generic and can be used in different Java contexts.
Related discussion on the subject. From [~moon]:
{quote}
[~tzolov] generalizing Dependency implementation is definitely a direction (along with generalizing ZeppelinContext). We can think two different level of generalize.
1) generalize dependency downloading
Generalize package [org.apache.zeppelin.spark.dep](https://github.com/apache/incubator-zeppelin/tree/master/spark/src/main/java/org/apache/zeppelin/spark/dep)
2) generalize dependency interpreter
Generalize package [org.apache.zeppelin.spark.dep](https://github.com/apache/incubator-zeppelin/tree/master/spark/src/main/java/org/apache/zeppelin/spark/dep) and [DepInterpreter](https://github.com/apache/incubator-zeppelin/blob/master/spark/src/main/java/org/apache/zeppelin/spark/DepInterpreter.java)
{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)