Github user selvinsource commented on the issue:
https://github.com/apache/zeppelin/pull/3157
@zjffdu this PR is a start. As I said I still need to add Utils methods
specific to Jet, in particular the Utils that convert the Jet DAG pipeline to a
network graph using Zeppelin display system. If we don't have an Hazelcast Jet
interpreter where would we put that code? It doesn't belong to the Java
interpreter.
Also, when the Java interpreter will be moved to JShell API (for which I
created a JIRA issue), there is a lot more that can be added to the Hazelcast
Jet interpreter like configuring the JetInstance (being a client or a node of
the cluster) in the interpreter properties so the user don't need to do that
for every note or paragraph.
You could say the same for the Beam interpreter, right now it extends the
Java interpreter and simply add some dependencies, however I still see value in
that so that the end user can just code beam without worrying about the so many
dependencies required.
Let me know what you think before I proceed in working on the Jet specific
Utils methods.
---
