mirror of https://github.com/apache/zeppelin synced 2026-05-24 09:38:26 +00:00

History

Jeff Zhang 0910e7f5b7 ZEPPELIN-3774. Rename module interpreter-parent to zeppelin-interpreter-parent ### What is this PR for? Trivial PR for module name refactoring. ### What type of PR is it? [Refactoring] ### Todos * [ ] - Task ### What is the Jira issue? * https://issues.apache.org/jira/browse/ZEPPELIN-3774 ### How should this be tested? * CI pass ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? No Author: Jeff Zhang <zjffdu@apache.org> Closes #3175 from zjffdu/ZEPPELIN-3774 and squashes the following commits: `ea72df9e5` [Jeff Zhang] ZEPPELIN-3774. Rename module interpreter-parent to zeppelin-interpreter-parent		2018-09-11 15:47:17 +08:00
..
src	Revert "[ZEPPELIN-3740] Adopt `google-java-format` and `fmt-maven-plugin`"	2018-08-29 19:05:55 +09:00
pom.xml	ZEPPELIN-3774. Rename module interpreter-parent to zeppelin-interpreter-parent	2018-09-11 15:47:17 +08:00
README.md	[ZEPPELIN-3653] - New Java interpreter	2018-08-03 09:15:19 +08:00

Overview

Java interpreter for Apache Zeppelin

Architecture

Current interpreter implementation supports the static REPL. It compiles the code in memory, execute it and redirect the output to Zeppelin.

Upon starting an interpreter, an instance of JavaCompiler is created.
When the user runs commands with java, the JavaParser go through the code to get a class that contains the main method.
Then it replaces the class name with random class name to avoid overriding while compilation. It creates new out & err stream to get the data in new stream instead of the console, to redirect output to Zeppelin.
If there is any error during compilation, it can catch and redirect to Zeppelin.
JavaInterpreterUtils contains useful methods to print out Java collections and leverage Zeppelin's built in visualization.