Elgato_dark/zeppelin
1
0
Fork 0
mirror of https://github.com/apache/zeppelin synced 2026-05-24 09:38:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Revert "ZEPPELIN-959: Fix odd code blocks in some documentations"

Browse source 
This reverts commit 967b2fa5e7.
This commit is contained in:
AhyoungRyu 2016-06-05 22:26:09 -07:00
parent 967b2fa5e7
commit 879b8f9a37
2 changed files with 1 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/development/writingzeppelininterpreter.md
View file

@ -39,13 +39,11 @@ Creating a new interpreter is quite simple. Just extend [org.apache.zeppelin.int
You can include `org.apache.zeppelin:zeppelin-interpreter:[VERSION]` artifact in your build system. And you should your jars under your interpreter directory with specific directory name. Zeppelin server reads interpreter directories recursively and initializes interpreters including your own interpreter.
There are three locations where you can store your interpreter group, name and other information. Zeppelin server tries to find the location below. Next, Zeppelin tries to find `interpareter-setting.json` in your interpreter jar.
```
{ZEPPELIN_INTERPRETER_DIR}/{YOUR_OWN_INTERPRETER_DIR}/interpreter-setting.json
```
Here is an example of `interpareter-setting.json` on your own interpreter.
```json
[
{
@ -74,13 +72,11 @@ Here is an example of `interpareter-setting.json` on your own interpreter.
```
Finally, Zeppelin uses static initialization with the following:
```
static {
Interpreter.register("MyInterpreterName", MyClassName.class.getName());
}
```
**Static initialization is deprecated and will be supported until 0.6.0.**
The name will appear later in the interpreter name option box during the interpreter configuration process.

3
docs/storage/storage.md
View file

@ -114,7 +114,6 @@ export ZEPPELIN_NOTEBOOK_S3_KMS_KEY_ID = kms-key-id
```
Or using the following setting in **zeppelin-site.xml**:
```
<property>
<name>zeppelin.notebook.s3.kmsKeyID</name>
@ -133,7 +132,6 @@ export ZEPPELIN_NOTEBOOK_S3_EMP = class-name
```
Or using the following setting in **zeppelin-site.xml**:
```
<property>
<name>zeppelin.notebook.s3.encryptionMaterialsProvider</name>
@ -146,6 +144,7 @@ Or using the following setting in **zeppelin-site.xml**:
Using `AzureNotebookRepo` you can connect your Zeppelin with your Azure account for notebook storage.
</br>
First of all, input your `AccountName`, `AccountKey`, and `Share Name` in the file **zeppelin-site.xml** by commenting out and completing the next properties: