Per note session -> Separate Interpreter for each note

This commit is contained in:
Lee moon soo 2016-02-23 11:27:57 -08:00
parent 7b073f6047
commit 4d2533f0e0
6 changed files with 6 additions and 6 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 35 KiB

After

Width:  |  Height:  |  Size: 37 KiB

View file

@ -30,7 +30,7 @@ Interpreters in the same InterpreterGroup can reference each other. For example,
InterpreterSetting is configuration of a given InterpreterGroup and a unit of start/stop interpreter.
All Interpreters in the same InterpreterSetting are launched in a single, separate JVM process. The Interpreter communicates with Zeppelin engine via thrift.
In 'per note session' mode, new Interpreter instance will be created per notebook. But it still runs on the same JVM while they're in the same InterpreterSettings.
In 'Separate Interpreter for each note' mode, new Interpreter instance will be created per notebook. But it still runs on the same JVM while they're in the same InterpreterSettings.
### Make your own Interpreter

View file

@ -264,9 +264,9 @@ select * from ${table=defaultTableName} where text like '%${search}%'
To learn more about dynamic form, checkout [Dynamic Form](../manual/dynamicform.html).
### Per note session
### Separate Interpreter for each note
In 'Per note session' mode, SparkInterpreter creates scala compiler per each notebook. However it still shares the single SparkContext.
In 'Separate Interpreter for each note' mode, SparkInterpreter creates scala compiler per each notebook. However it still shares the single SparkContext.
## Setting up Zeppelin with Kerberos
Logical setup with Zeppelin, Kerberos Distribution Center (KDC), and Spark on YARN:

View file

@ -55,7 +55,7 @@ Each interpreters is belonged to a single group and registered together. All of
## Interpreter binding mode
Each Interpreter Setting can choose one of two different interpreter binding mode.
Shared mode (default) and 'Per note session' mode. In shared mode, every notebook binded to the Interpreter Setting will share the single Interpreter instance. In 'Per note session' mode, each notebook will create new Interpreter instance. Therefore each notebook will have fresh new Interpreter environment.
Shared mode (default) and 'Separate Interpreter for each note' mode. In shared mode, every notebook binded to the Interpreter Setting will share the single Interpreter instance. In 'Separate Interpreter for each note' mode, each notebook will create new Interpreter instance. Therefore each notebook will have fresh new Interpreter environment.
<img src="/assets/themes/zeppelin/img/screenshots/interpreter_persession.png" width="400px">

View file

@ -37,7 +37,7 @@ limitations under the License.
<b>Option</b>
<div class="checkbox">
<label><input type="checkbox" style="top:-5px" ng-model="newInterpreterSetting.option.perNoteSession">Per note session</input></label>
<label><input type="checkbox" style="top:-5px" ng-model="newInterpreterSetting.option.perNoteSession">Separate Interpreter for each note</input></label>
</div>
<b>Properties</b>

View file

@ -117,7 +117,7 @@ limitations under the License.
style="top:-5px"
ng-disabled="!valueform.$visible"
ng-model="setting.option.perNoteSession">
Per note session</input>
Separate Interpreter for each note</input>
</label>
</div>
</div>