Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1574
@Leemoonsoo @felixcheung I update this PR, please help help review that. My
purpose is to make ZeppelinContext extensible is in 2 perspective.
* All the interpreter can has its own ZeppelinContext. e.g. My next PR
would to implement FlinkZeppelinContext which would display flink DataSet/Table
data in zeppelin's table format
* Interpreters can also add customized features for its own
ZeppelinContext. e.g. SparkZeppelinContext can add one extention point to allow
user to visualize mllib model in zeppelin.
Communication between interpreter group mentioned by @felixcheung above is
not implemented in this PR as I think this would bring much large change and
need more sophisticated design. But we could put it in `BaseZeppelinContext` in
future when we want to implement it.
---
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.
---
