You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by "Xun Liu (JIRA)" <ji...@apache.org> on 2019/02/25 08:20:00 UTC

[jira] [Created] (ZEPPELIN-4019) Interpreter process get the notes from zeppelin server

Xun Liu created ZEPPELIN-4019:
---------------------------------

             Summary: Interpreter process get the notes from zeppelin server
                 Key: ZEPPELIN-4019
                 URL: https://issues.apache.org/jira/browse/ZEPPELIN-4019
             Project: Zeppelin
          Issue Type: Sub-task
    Affects Versions: 0.9.0
            Reporter: Xun Liu
            Assignee: Xun Liu


Now, the interpreter is executed according to the paragraph. Click the run button in the paragraph, and only the code content in the current paragraph can be obtained in the interpreter process.

To pass the Dashboard paragraph in the submarine interpreter, you need to submit all the code content in this note to tensorflow for execution.

So, I think need to get the note data in sever through `RemoteInterpreterEventServer` in the interpreter process.

I implemented two other methods, so that the interpreter can get the note in the server, the actual running effect is not the best solution.
1) By having the interpreter directly access the external storage of the note repository, such as HDFS, S3.
1. But this limits the need to store notes in an external storage system.
2. In hdfs with kerberos authentication system enabled, not all users can access the note folder.

2) Get the note from the server from the REST client in the interpreter.
1. Need to let zeppelin/api/notes intercept in shrio.ini.
2. Or let the interpreter access the REST interface of the server through the user and password, but it is not safe.

In addition, inĀ [ZEPPELIN-4018 Workflow and orchestration|https://issues.apache.org/jira/browse/ZEPPELIN-4018], it is also necessary to query all the notes and paragraphs of the user in the workflow paragraph for the execution of the note.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)