[jira] [Updated] (SUBMARINE-232) [Umbrella] Custom Zeppelin Submodule

["Wei-Chiu Chuang (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SUBMARINE-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei-Chiu Chuang updated SUBMARINE-232:
--------------------------------------
    Issue Type: New Feature  (was: Bug)

> [Umbrella] Custom Zeppelin Submodule
> ------------------------------------
>
>                 Key: SUBMARINE-232
>                 URL: https://issues.apache.org/jira/browse/SUBMARINE-232
>             Project: Hadoop Submarine
>          Issue Type: New Feature
>          Components: Submodule Zeppelin
>            Reporter: Liu Xun
>            Assignee: Liu Xun
>            Priority: Major
>             Fix For: 0.4.0
>
>
> 2. Interpreter
> Submarine provides multi-language execution for notebooks in workbench through interpreters in a variety of programming languages (for example, python interpreter, spark interpreter).
> 2.1 Interpreter execution flow
> 1. The user enters the code in the workbench notebook and clicks the execute button. First the workbench server starts the interpreter process.
> 2. The workbench server sends the user's code to the interpreter process via the interface for execution, and gets the execution result, returning to the workbench notebook for display.
> 2.2 Integrate Zeppelin Interpreter
> Zeppelin has this mature multilingual interpreter that can be introduced for use as a Submarine interpreter, but Submarine has some specific requirements for the use of the interpreter, such as Submarine's need to extend the interface of the Zeppelin interpreter, etc., so Zeppelin is required. The interface layer of the interpreter is modified to some extent.
> At the same time, in order to be consistent with the development of the Zeppelin interpreter, we used submodule to customize the Zeppelin interpreter to a certain extent.
> Design Doc: https://docs.google.com/document/d/1LJc5hRTWfIs6K5f7vMgGC_FUizeQf-qqiWICqO8SoR8/edit#



--
This message was sent by Atlassian Jira
(v8.3.4#803005)