You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@zeppelin.apache.org by mo...@apache.org on 2015/11/18 01:08:33 UTC
[3/4] incubator-zeppelin git commit: ZEPPELIN-412 Documentation based
on Zeppelin version
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/interpreter/cassandra.md
----------------------------------------------------------------------
diff --git a/docs/docs/interpreter/cassandra.md b/docs/docs/interpreter/cassandra.md
deleted file mode 100644
index b53295c..0000000
--- a/docs/docs/interpreter/cassandra.md
+++ /dev/null
@@ -1,807 +0,0 @@
----
-layout: page
-title: "Cassandra Interpreter"
-description: "Cassandra Interpreter"
-group: manual
----
-{% include JB/setup %}
-
-<hr/>
-## 1. Cassandra CQL Interpreter for Apache Zeppelin
-
-<br/>
-<table class="table-configuration">
- <tr>
- <th>Name</th>
- <th>Class</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>%cassandra</td>
- <td>CassandraInterpreter</td>
- <td>Provides interpreter for Apache Cassandra CQL query language</td>
- </tr>
-</table>
-
-<hr/>
-
-## 2. Enabling Cassandra Interpreter
-
- In a notebook, to enable the **Cassandra** interpreter, click on the **Gear** icon and select **Cassandra**
-
- <center>
- 
-
- 
- </center>
-
-<hr/>
-
-## 3. Using the Cassandra Interpreter
-
- In a paragraph, use **_%cassandra_** to select the **Cassandra** interpreter and then input all commands.
-
- To access the interactive help, type **HELP;**
-
- <center>
- 
- </center>
-
-<hr/>
-
-## 4. Interpreter Commands
-
- The **Cassandra** interpreter accepts the following commands
-
-<center>
- <table class="table-configuration">
- <tr>
- <th>Command Type</th>
- <th>Command Name</th>
- <th>Description</th>
- </tr>
- <tr>
- <td nowrap>Help command</td>
- <td>HELP</td>
- <td>Display the interactive help menu</td>
- </tr>
- <tr>
- <td nowrap>Schema commands</td>
- <td>DESCRIBE KEYSPACE, DESCRIBE CLUSTER, DESCRIBE TABLES ...</td>
- <td>Custom commands to describe the Cassandra schema</td>
- </tr>
- <tr>
- <td nowrap>Option commands</td>
- <td>@consistency, @retryPolicy, @fetchSize ...</td>
- <td>Inject runtime options to all statements in the paragraph</td>
- </tr>
- <tr>
- <td nowrap>Prepared statement commands</td>
- <td>@prepare, @bind, @remove_prepared</td>
- <td>Let you register a prepared command and re-use it later by injecting bound values</td>
- </tr>
- <tr>
- <td nowrap>Native CQL statements</td>
- <td>All CQL-compatible statements (SELECT, INSERT, CREATE ...)</td>
- <td>All CQL statements are executed directly against the Cassandra server</td>
- </tr>
- </table>
-</center>
-
-<hr/>
-## 5. CQL statements
-
-This interpreter is compatible with any CQL statement supported by Cassandra. Ex:
-
-```sql
-
- INSERT INTO users(login,name) VALUES('jdoe','John DOE');
- SELECT * FROM users WHERE login='jdoe';
-```
-
-Each statement should be separated by a semi-colon ( **;** ) except the special commands below:
-
-1. @prepare
-2. @bind
-3. @remove_prepare
-4. @consistency
-5. @serialConsistency
-6. @timestamp
-7. @retryPolicy
-8. @fetchSize
-
-Multi-line statements as well as multiple statements on the same line are also supported as long as they are
-separated by a semi-colon. Ex:
-
-```sql
-
- USE spark_demo;
-
- SELECT * FROM albums_by_country LIMIT 1; SELECT * FROM countries LIMIT 1;
-
- SELECT *
- FROM artists
- WHERE login='jlennon';
-```
-
-Batch statements are supported and can span multiple lines, as well as DDL(CREATE/ALTER/DROP) statements:
-
-```sql
-
- BEGIN BATCH
- INSERT INTO users(login,name) VALUES('jdoe','John DOE');
- INSERT INTO users_preferences(login,account_type) VALUES('jdoe','BASIC');
- APPLY BATCH;
-
- CREATE TABLE IF NOT EXISTS test(
- key int PRIMARY KEY,
- value text
- );
-```
-
-CQL statements are <strong>case-insensitive</strong> (except for column names and values).
-This means that the following statements are equivalent and valid:
-
-```sql
-
- INSERT INTO users(login,name) VALUES('jdoe','John DOE');
- Insert into users(login,name) vAlues('hsue','Helen SUE');
-```
-
-The complete list of all CQL statements and versions can be found below:
-<center>
- <table class="table-configuration">
- <tr>
- <th>Cassandra Version</th>
- <th>Documentation Link</th>
- </tr>
- <tr>
- <td><strong>2.2</strong></td>
- <td>
- <a target="_blank"
- href="http://docs.datastax.com/en/cql/3.3/cql/cqlIntro.html">
- http://docs.datastax.com/en/cql/3.3/cql/cqlIntro.html
- </a>
- </td>
- </tr>
- <tr>
- <td><strong>2.1 & 2.0</strong></td>
- <td>
- <a target="_blank"
- href="http://docs.datastax.com/en/cql/3.1/cql/cql_intro_c.html">
- http://docs.datastax.com/en/cql/3.1/cql/cql_intro_c.html
- </a>
- </td>
- </tr>
- <tr>
- <td><strong>1.2</strong></td>
- <td>
- <a target="_blank"
- href="http://docs.datastax.com/en/cql/3.0/cql/aboutCQL.html">
- http://docs.datastax.com/en/cql/3.0/cql/aboutCQL.html
- </a>
- </td>
- </tr>
- </table>
-</center>
-
-<hr/>
-
-## 6. Comments in statements
-
-It is possible to add comments between statements. Single line comments start with the hash sign (#). Multi-line comments are enclosed between /** and **/. Ex:
-
-```sql
-
- #First comment
- INSERT INTO users(login,name) VALUES('jdoe','John DOE');
-
- /**
- Multi line
- comments
- **/
- Insert into users(login,name) vAlues('hsue','Helen SUE');
-```
-
-<hr/>
-
-## 7. Syntax Validation
-
-The interpreters is shipped with a built-in syntax validator. This validator only checks for basic syntax errors.
-All CQL-related syntax validation is delegated directly to **Cassandra**
-
-Most of the time, syntax errors are due to **missing semi-colons** between statements or **typo errors**.
-
-<hr/>
-
-## 8. Schema commands
-
-To make schema discovery easier and more interactive, the following commands are supported:
-<center>
- <table class="table-configuration">
- <tr>
- <th>Command</th>
- <th>Description</th>
- </tr>
- <tr>
- <td><strong>DESCRIBE CLUSTER;</strong></td>
- <td>Show the current cluster name and its partitioner</td>
- </tr>
- <tr>
- <td><strong>DESCRIBE KEYSPACES;</strong></td>
- <td>List all existing keyspaces in the cluster and their configuration (replication factor, durable write ...)</td>
- </tr>
- <tr>
- <td><strong>DESCRIBE TABLES;</strong></td>
- <td>List all existing keyspaces in the cluster and for each, all the tables name</td>
- </tr>
- <tr>
- <td><strong>DESCRIBE TYPES;</strong></td>
- <td>List all existing user defined types in the <strong>current (logged) keyspace</strong></td>
- </tr>
- <tr>
- <td nowrap><strong>DESCRIBE FUNCTIONS <keyspace_name>;</strong></td>
- <td>List all existing user defined functions in the given keyspace</td>
- </tr>
- <tr>
- <td nowrap><strong>DESCRIBE AGGREGATES <keyspace_name>;</strong></td>
- <td>List all existing user defined aggregates in the given keyspace</td>
- </tr>
- <tr>
- <td nowrap><strong>DESCRIBE KEYSPACE <keyspace_name>;</strong></td>
- <td>Describe the given keyspace configuration and all its table details (name, columns, ...)</td>
- </tr>
- <tr>
- <td nowrap><strong>DESCRIBE TABLE (<keyspace_name>).<table_name>;</strong></td>
- <td>
- Describe the given table. If the keyspace is not provided, the current logged in keyspace is used.
- If there is no logged in keyspace, the default system keyspace is used.
- If no table is found, an error message is raised
- </td>
- </tr>
- <tr>
- <td nowrap><strong>DESCRIBE TYPE (<keyspace_name>).<type_name>;</strong></td>
- <td>
- Describe the given type(UDT). If the keyspace is not provided, the current logged in keyspace is used.
- If there is no logged in keyspace, the default system keyspace is used.
- If no type is found, an error message is raised
- </td>
- </tr>
- <tr>
- <td nowrap><strong>DESCRIBE FUNCTION (<keyspace_name>).<function_name>;</strong></td>
- <td>Describe the given user defined function. The keyspace is optional</td>
- </tr>
- <tr>
- <td nowrap><strong>DESCRIBE AGGREGATE (<keyspace_name>).<aggregate_name>;</strong></td>
- <td>Describe the given user defined aggregate. The keyspace is optional</td>
- </tr>
- </table>
-</center>
-
-The schema objects (cluster, keyspace, table, type, function and aggregate) are displayed in a tabular format.
-There is a drop-down menu on the top left corner to expand objects details. On the top right menu is shown the Icon legend.
-
-<br/>
-<center>
- 
-</center>
-
-<hr/>
-
-## 9. Runtime Parameters
-
-Sometimes you want to be able to pass runtime query parameters to your statements.
-Those parameters are not part of the CQL specs and are specific to the interpreter.
-Below is the list of all parameters:
-
-<br/>
-<center>
- <table class="table-configuration">
- <tr>
- <th>Parameter</th>
- <th>Syntax</th>
- <th>Description</th>
- </tr>
- <tr>
- <td nowrap>Consistency Level</td>
- <td><strong>@consistency=<em>value</em></strong></td>
- <td>Apply the given consistency level to all queries in the paragraph</td>
- </tr>
- <tr>
- <td nowrap>Serial Consistency Level</td>
- <td><strong>@serialConsistency=<em>value</em></strong></td>
- <td>Apply the given serial consistency level to all queries in the paragraph</td>
- </tr>
- <tr>
- <td nowrap>Timestamp</td>
- <td><strong>@timestamp=<em>long value</em></strong></td>
- <td>
- Apply the given timestamp to all queries in the paragraph.
- Please note that timestamp value passed directly in CQL statement will override this value
- </td>
- </tr>
- <tr>
- <td nowrap>Retry Policy</td>
- <td><strong>@retryPolicy=<em>value</em></strong></td>
- <td>Apply the given retry policy to all queries in the paragraph</td>
- </tr>
- <tr>
- <td nowrap>Fetch Size</td>
- <td><strong>@fetchSize=<em>integer value</em></strong></td>
- <td>Apply the given fetch size to all queries in the paragraph</td>
- </tr>
- </table>
-</center>
-
- Some parameters only accept restricted values:
-
-<br/>
-<center>
- <table class="table-configuration">
- <tr>
- <th>Parameter</th>
- <th>Possible Values</th>
- </tr>
- <tr>
- <td nowrap>Consistency Level</td>
- <td><strong>ALL, ANY, ONE, TWO, THREE, QUORUM, LOCAL_ONE, LOCAL_QUORUM, EACH_QUORUM</strong></td>
- </tr>
- <tr>
- <td nowrap>Serial Consistency Level</td>
- <td><strong>SERIAL, LOCAL_SERIAL</strong></td>
- </tr>
- <tr>
- <td nowrap>Timestamp</td>
- <td>Any long value</td>
- </tr>
- <tr>
- <td nowrap>Retry Policy</td>
- <td><strong>DEFAULT, DOWNGRADING_CONSISTENCY, FALLTHROUGH, LOGGING_DEFAULT, LOGGING_DOWNGRADING, LOGGING_FALLTHROUGH</strong></td>
- </tr>
- <tr>
- <td nowrap>Fetch Size</td>
- <td>Any integer value</td>
- </tr>
- </table>
-</center>
-
->Please note that you should **not** add semi-colon ( **;** ) at the end of each parameter statement
-
-Some examples:
-
-```sql
-
- CREATE TABLE IF NOT EXISTS spark_demo.ts(
- key int PRIMARY KEY,
- value text
- );
- TRUNCATE spark_demo.ts;
-
- # Timestamp in the past
- @timestamp=10
-
- # Force timestamp directly in the first insert
- INSERT INTO spark_demo.ts(key,value) VALUES(1,'first insert') USING TIMESTAMP 100;
-
- # Select some data to make the clock turn
- SELECT * FROM spark_demo.albums LIMIT 100;
-
- # Now insert using the timestamp parameter set at the beginning(10)
- INSERT INTO spark_demo.ts(key,value) VALUES(1,'second insert');
-
- # Check for the result. You should see 'first insert'
- SELECT value FROM spark_demo.ts WHERE key=1;
-```
-
-Some remarks about query parameters:
-
-> 1. **many** query parameters can be set in the same paragraph
-> 2. if the **same** query parameter is set many time with different values, the interpreter only take into account the first value
-> 3. each query parameter applies to **all CQL statements** in the same paragraph, unless you override the option using plain CQL text (like forcing timestamp with the USING clause)
-> 4. the order of each query parameter with regard to CQL statement does not matter
-
-<hr/>
-
-## 10. Support for Prepared Statements
-
-For performance reason, it is better to prepare statements before-hand and reuse them later by providing bound values.
-This interpreter provides 3 commands to handle prepared and bound statements:
-
-1. **@prepare**
-2. **@bind**
-3. **@remove_prepared**
-
-Example:
-
-```
-
- @prepare[statement_name]=...
-
- @bind[statement_name]=’text’, 1223, ’2015-07-30 12:00:01’, null, true, [‘list_item1’, ’list_item2’]
-
- @bind[statement_name_with_no_bound_value]
-
- @remove_prepare[statement_name]
-```
-
-<br/>
-#### a. @prepare
-<br/>
-You can use the syntax _"@prepare[statement_name]=SELECT ..."_ to create a prepared statement.
-The _statement_name_ is **mandatory** because the interpreter prepares the given statement with the Java driver and
-saves the generated prepared statement in an **internal hash map**, using the provided _statement_name_ as search key.
-
-> Please note that this internal prepared statement map is shared with **all notebooks** and **all paragraphs** because
-there is only one instance of the interpreter for Cassandra
-
-> If the interpreter encounters **many** @prepare for the **same _statement_name_ (key)**, only the **first** statement will be taken into account.
-
-Example:
-
-```
-
- @prepare[select]=SELECT * FROM spark_demo.albums LIMIT ?
-
- @prepare[select]=SELECT * FROM spark_demo.artists LIMIT ?
-```
-
-For the above example, the prepared statement is _SELECT * FROM spark_demo.albums LIMIT ?_.
-_SELECT * FROM spark_demo.artists LIMIT ?_ is ignored because an entry already exists in the prepared statements map with the key select.
-
-In the context of **Zeppelin**, a notebook can be scheduled to be executed at regular interval,
-thus it is necessary to **avoid re-preparing many time the same statement (considered an anti-pattern)**.
-<br/>
-<br/>
-#### b. @bind
-<br/>
-Once the statement is prepared (possibly in a separated notebook/paragraph). You can bind values to it:
-
-```
- @bind[select_first]=10
-```
-
-Bound values are not mandatory for the **@bind** statement. However if you provide bound values, they need to comply to some syntax:
-
-* String values should be enclosed between simple quotes ( ‘ )
-* Date values should be enclosed between simple quotes ( ‘ ) and respect the formats:
- 1. yyyy-MM-dd HH:MM:ss
- 2. yyyy-MM-dd HH:MM:ss.SSS
-* **null** is parsed as-is
-* **boolean** (true|false) are parsed as-is
-* collection values must follow the **[standard CQL syntax]**:
- * list: [‘list_item1’, ’list_item2’, ...]
- * set: {‘set_item1’, ‘set_item2’, …}
- * map: {‘key1’: ‘val1’, ‘key2’: ‘val2’, …}
-* **tuple** values should be enclosed between parenthesis (see **[Tuple CQL syntax]**): (‘text’, 123, true)
-* **udt** values should be enclosed between brackets (see **[UDT CQL syntax]**): {stree_name: ‘Beverly Hills’, number: 104, zip_code: 90020, state: ‘California’, …}
-
-> It is possible to use the @bind statement inside a batch:
->
-> ```sql
->
-> BEGIN BATCH
-> @bind[insert_user]='jdoe','John DOE'
-> UPDATE users SET age = 27 WHERE login='hsue';
-> APPLY BATCH;
-> ```
-
-<br/>
-#### c. @remove_prepare
-<br/>
-To avoid for a prepared statement to stay forever in the prepared statement map, you can use the
-**@remove_prepare[statement_name]** syntax to remove it.
-Removing a non-existing prepared statement yields no error.
-
-<hr/>
-
-## 11. Using Dynamic Forms
-
-Instead of hard-coding your CQL queries, it is possible to use the mustache syntax ( **\{\{ \}\}** ) to inject simple value or multiple choices forms.
-
-The syntax for simple parameter is: **\{\{input_Label=default value\}\}**. The default value is mandatory because the first time the paragraph is executed,
-we launch the CQL query before rendering the form so at least one value should be provided.
-
-The syntax for multiple choices parameter is: **\{\{input_Label=value1 | value2 | … | valueN \}\}**. By default the first choice is used for CQL query
-the first time the paragraph is executed.
-
-Example:
-
-{% raw %}
- #Secondary index on performer style
- SELECT name, country, performer
- FROM spark_demo.performers
- WHERE name='{{performer=Sheryl Crow|Doof|Fanfarlo|Los Paranoia}}'
- AND styles CONTAINS '{{style=Rock}}';
-{% endraw %}
-
-
-In the above example, the first CQL query will be executed for _performer='Sheryl Crow' AND style='Rock'_.
-For subsequent queries, you can change the value directly using the form.
-
-> Please note that we enclosed the **\{\{ \}\}** block between simple quotes ( **'** ) because Cassandra expects a String here.
-> We could have also use the **\{\{style='Rock'\}\}** syntax but this time, the value displayed on the form is **_'Rock'_** and not **_Rock_**.
-
-It is also possible to use dynamic forms for **prepared statements**:
-
-{% raw %}
-
- @bind[select]=='{{performer=Sheryl Crow|Doof|Fanfarlo|Los Paranoia}}', '{{style=Rock}}'
-
-{% endraw %}
-
-<hr/>
-
-## 12. Execution parallelism and shared states
-
-It is possible to execute many paragraphs in parallel. However, at the back-end side, we’re still using synchronous queries.
-_Asynchronous execution_ is only possible when it is possible to return a `Future` value in the `InterpreterResult`.
-It may be an interesting proposal for the **Zeppelin** project.
-
-Another caveat is that the same `com.datastax.driver.core.Session` object is used for **all** notebooks and paragraphs.
-Consequently, if you use the **USE _keyspace name_;** statement to log into a keyspace, it will change the keyspace for
-**all current users** of the **Cassandra** interpreter because we only create 1 `com.datastax.driver.core.Session` object
-per instance of **Cassandra** interpreter.
-
-The same remark does apply to the **prepared statement hash map**, it is shared by **all users** using the same instance of **Cassandra** interpreter.
-
-Until **Zeppelin** offers a real multi-users separation, there is a work-around to segregate user environment and states:
-_create different **Cassandra** interpreter instances_
-
-For this, first go to the **Interpreter** menu and click on the **Create** button
-<br/>
-<br/>
-<center>
- 
-</center>
-
-In the interpreter creation form, put **cass-instance2** as **Name** and select the **cassandra**
-in the interpreter drop-down list
-<br/>
-<br/>
-<center>
- 
-</center>
-
- Click on **Save** to create the new interpreter instance. Now you should be able to see it in the interpreter list.
-
-<br/>
-<br/>
-<center>
- 
-</center>
-
-Go back to your notebook and click on the **Gear** icon to configure interpreter bindings.
-You should be able to see and select the **cass-instance2** interpreter instance in the available
-interpreter list instead of the standard **cassandra** instance.
-
-<br/>
-<br/>
-<center>
- 
-</center>
-
-<hr/>
-
-## 13. Interpreter Configuration
-
-To configure the **Cassandra** interpreter, go to the **Interpreter** menu and scroll down to change the parameters.
-The **Cassandra** interpreter is using the official **[Cassandra Java Driver]** and most of the parameters are used
-to configure the Java driver
-
-Below are the configuration parameters and their default value.
-
-
- <table class="table-configuration">
- <tr>
- <th>Property Name</th>
- <th>Description</th>
- <th>Default Value</th>
- </tr>
- <tr>
- <td>cassandra.cluster</td>
- <td>Name of the Cassandra cluster to connect to</td>
- <td>Test Cluster</td>
- </tr>
- <tr>
- <td>cassandra.compression.protocol</td>
- <td>On wire compression. Possible values are: NONE, SNAPPY, LZ4</td>
- <td>NONE</td>
- </tr>
- <tr>
- <td>cassandra.credentials.username</td>
- <td>If security is enable, provide the login</td>
- <td>none</td>
- </tr>
- <tr>
- <td>cassandra.credentials.password</td>
- <td>If security is enable, provide the password</td>
- <td>none</td>
- </tr>
- <tr>
- <td>cassandra.hosts</td>
- <td>
- Comma separated Cassandra hosts (DNS name or IP address).
- <br/>
- Ex: '192.168.0.12,node2,node3'
- </td>
- <td>localhost</td>
- </tr>
- <tr>
- <td>cassandra.interpreter.parallelism</td>
- <td>Number of concurrent paragraphs(queries block) that can be executed</td>
- <td>10</td>
- </tr>
- <tr>
- <td>cassandra.keyspace</td>
- <td>
- Default keyspace to connect to.
- <strong>
- It is strongly recommended to let the default value
- and prefix the table name with the actual keyspace
- in all of your queries
- </strong>
- </td>
- <td>system</td>
- </tr>
- <tr>
- <td>cassandra.load.balancing.policy</td>
- <td>
- Load balancing policy. Default = <em>new TokenAwarePolicy(new DCAwareRoundRobinPolicy())</em>
- To Specify your own policy, provide the <strong>fully qualify class name (FQCN)</strong> of your policy.
- At runtime the interpreter will instantiate the policy using
- <strong>Class.forName(FQCN)</strong>
- </td>
- <td>DEFAULT</td>
- </tr>
- <tr>
- <td>cassandra.max.schema.agreement.wait.second</td>
- <td>Cassandra max schema agreement wait in second</td>
- <td>10</td>
- </tr>
- <tr>
- <td>cassandra.pooling.core.connection.per.host.local</td>
- <td>Protocol V2 and below default = 2. Protocol V3 and above default = 1</td>
- <td>2</td>
- </tr>
- <tr>
- <td>cassandra.pooling.core.connection.per.host.remote</td>
- <td>Protocol V2 and below default = 1. Protocol V3 and above default = 1</td>
- <td>1</td>
- </tr>
- <tr>
- <td>cassandra.pooling.heartbeat.interval.seconds</td>
- <td>Cassandra pool heartbeat interval in secs</td>
- <td>30</td>
- </tr>
- <tr>
- <td>cassandra.pooling.idle.timeout.seconds</td>
- <td>Cassandra idle time out in seconds</td>
- <td>120</td>
- </tr>
- <tr>
- <td>cassandra.pooling.max.connection.per.host.local</td>
- <td>Protocol V2 and below default = 8. Protocol V3 and above default = 1</td>
- <td>8</td>
- </tr>
- <tr>
- <td>cassandra.pooling.max.connection.per.host.remote</td>
- <td>Protocol V2 and below default = 2. Protocol V3 and above default = 1</td>
- <td>2</td>
- </tr>
- <tr>
- <td>cassandra.pooling.max.request.per.connection.local</td>
- <td>Protocol V2 and below default = 128. Protocol V3 and above default = 1024</td>
- <td>128</td>
- </tr>
- <tr>
- <td>cassandra.pooling.max.request.per.connection.remote</td>
- <td>Protocol V2 and below default = 128. Protocol V3 and above default = 256</td>
- <td>128</td>
- </tr>
- <tr>
- <td>cassandra.pooling.new.connection.threshold.local</td>
- <td>Protocol V2 and below default = 100. Protocol V3 and above default = 800</td>
- <td>100</td>
- </tr>
- <tr>
- <td>cassandra.pooling.new.connection.threshold.remote</td>
- <td>Protocol V2 and below default = 100. Protocol V3 and above default = 200</td>
- <td>100</td>
- </tr>
- <tr>
- <td>cassandra.pooling.pool.timeout.millisecs</td>
- <td>Cassandra pool time out in millisecs</td>
- <td>5000</td>
- </tr>
- <tr>
- <td>cassandra.protocol.version</td>
- <td>Cassandra binary protocol version</td>
- <td>3</td>
- </tr>
- <tr>
- <td>cassandra.query.default.consistency</td>
- <td>
- Cassandra query default consistency level
- <br/>
- Available values: ONE, TWO, THREE, QUORUM, LOCAL_ONE, LOCAL_QUORUM, EACH_QUORUM, ALL
- </td>
- <td>ONE</td>
- </tr>
- <tr>
- <td>cassandra.query.default.fetchSize</td>
- <td>Cassandra query default fetch size</td>
- <td>5000</td>
- </tr>
- <tr>
- <td>cassandra.query.default.serial.consistency</td>
- <td>
- Cassandra query default serial consistency level
- <br/>
- Available values: SERIAL, LOCAL_SERIAL
- </td>
- <td>SERIAL</td>
- </tr>
- <tr>
- <td>cassandra.reconnection.policy</td>
- <td>
- Cassandra Reconnection Policy.
- Default = new ExponentialReconnectionPolicy(1000, 10 * 60 * 1000)
- To Specify your own policy, provide the <strong>fully qualify class name (FQCN)</strong> of your policy.
- At runtime the interpreter will instantiate the policy using
- <strong>Class.forName(FQCN)</strong>
- </td>
- <td>DEFAULT</td>
- </tr>
- <tr>
- <td>cassandra.retry.policy</td>
- <td>
- Cassandra Retry Policy.
- Default = DefaultRetryPolicy.INSTANCE
- To Specify your own policy, provide the <strong>fully qualify class name (FQCN)</strong> of your policy.
- At runtime the interpreter will instantiate the policy using
- <strong>Class.forName(FQCN)</strong>
- </td>
- <td>DEFAULT</td>
- </tr>
- <tr>
- <td>cassandra.socket.connection.timeout.millisecs</td>
- <td>Cassandra socket default connection timeout in millisecs</td>
- <td>500</td>
- </tr>
- <tr>
- <td>cassandra.socket.read.timeout.millisecs</td>
- <td>Cassandra socket read timeout in millisecs</td>
- <td>12000</td>
- </tr>
- <tr>
- <td>cassandra.socket.tcp.no_delay</td>
- <td>Cassandra socket TCP no delay</td>
- <td>true</td>
- </tr>
- <tr>
- <td>cassandra.speculative.execution.policy</td>
- <td>
- Cassandra Speculative Execution Policy.
- Default = NoSpeculativeExecutionPolicy.INSTANCE
- To Specify your own policy, provide the <strong>fully qualify class name (FQCN)</strong> of your policy.
- At runtime the interpreter will instantiate the policy using
- <strong>Class.forName(FQCN)</strong>
- </td>
- <td>DEFAULT</td>
- </tr>
- </table>
-
-<hr/>
-
-## 14. Bugs & Contacts
-
- If you encounter a bug for this interpreter, please create a **[JIRA]** ticket and ping me on Twitter
- at **[@doanduyhai]**
-
-
-[Cassandra Java Driver]: https://github.com/datastax/java-driver
-[standard CQL syntax]: http://docs.datastax.com/en/cql/3.1/cql/cql_using/use_collections_c.html
-[Tuple CQL syntax]: http://docs.datastax.com/en/cql/3.1/cql/cql_reference/tupleType.html
-[UDT CQL syntax]: http://docs.datastax.com/en/cql/3.1/cql/cql_using/cqlUseUDT.html
-[JIRA]: https://issues.apache.org/jira/browse/ZEPPELIN-382?jql=project%20%3D%20ZEPPELIN
-[@doanduyhai]: https://twitter.com/doanduyhai
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/interpreter/flink.md
----------------------------------------------------------------------
diff --git a/docs/docs/interpreter/flink.md b/docs/docs/interpreter/flink.md
deleted file mode 100644
index ce1f780..0000000
--- a/docs/docs/interpreter/flink.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-layout: page
-title: "Flink Interpreter"
-description: ""
-group: manual
----
-{% include JB/setup %}
-
-
-## Flink interpreter for Apache Zeppelin
-[Apache Flink](https://flink.apache.org) is an open source platform for distributed stream and batch data processing.
-
-
-### How to start local Flink cluster, to test the interpreter
-Zeppelin comes with pre-configured flink-local interpreter, which starts Flink in a local mode on your machine, so you do not need to install anything.
-
-### How to configure interpreter to point to Flink cluster
-At the "Interpreters" menu, you have to create a new Flink interpreter and provide next properties:
-
-<table class="table-configuration">
- <tr>
- <th>property</th>
- <th>value</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>host</td>
- <td>local</td>
- <td>host name of running JobManager. 'local' runs flink in local mode (default)</td>
- </tr>
- <tr>
- <td>port</td>
- <td>6123</td>
- <td>port of running JobManager</td>
- </tr>
- <tr>
- <td>xxx</td>
- <td>yyy</td>
- <td>anything else from [Flink Configuration](https://ci.apache.org/projects/flink/flink-docs-release-0.9/setup/config.html)</td>
- </tr>
-</table>
-<br />
-
-
-### How to test it's working
-
-In example, by using the [Zeppelin notebook](https://www.zeppelinhub.com/viewer/notebooks/aHR0cHM6Ly9yYXcuZ2l0aHVidXNlcmNvbnRlbnQuY29tL05GTGFicy96ZXBwZWxpbi1ub3RlYm9va3MvbWFzdGVyL25vdGVib29rcy8yQVFFREs1UEMvbm90ZS5qc29u) is from [Till Rohrmann's presentation](http://www.slideshare.net/tillrohrmann/data-analysis-49806564) "Interactive data analysis with Apache Flink" for Apache Flink Meetup.
-
-
-```
-%sh
-rm 10.txt.utf-8
-wget http://www.gutenberg.org/ebooks/10.txt.utf-8
-```
-```
-%flink
-case class WordCount(word: String, frequency: Int)
-val bible:DataSet[String] = env.readTextFile("10.txt.utf-8")
-val partialCounts: DataSet[WordCount] = bible.flatMap{
- line =>
- """\b\w+\b""".r.findAllIn(line).map(word => WordCount(word, 1))
-// line.split(" ").map(word => WordCount(word, 1))
-}
-val wordCounts = partialCounts.groupBy("word").reduce{
- (left, right) => WordCount(left.word, left.frequency + right.frequency)
-}
-val result10 = wordCounts.first(10).collect()
-```
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/interpreter/geode.md
----------------------------------------------------------------------
diff --git a/docs/docs/interpreter/geode.md b/docs/docs/interpreter/geode.md
deleted file mode 100644
index 96d1c04..0000000
--- a/docs/docs/interpreter/geode.md
+++ /dev/null
@@ -1,203 +0,0 @@
----
-layout: page
-title: "Geode OQL Interpreter"
-description: ""
-group: manual
----
-{% include JB/setup %}
-
-
-## Geode/Gemfire OQL Interpreter for Apache Zeppelin
-
-<br/>
-<table class="table-configuration">
- <tr>
- <th>Name</th>
- <th>Class</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>%geode.oql</td>
- <td>GeodeOqlInterpreter</td>
- <td>Provides OQL environment for Apache Geode</td>
- </tr>
-</table>
-
-<br/>
-This interpreter supports the [Geode](http://geode.incubator.apache.org/) [Object Query Language (OQL)](http://geode-docs.cfapps.io/docs/developing/querying_basics/oql_compared_to_sql.html). With the OQL-based querying language:
-
-[<img align="right" src="http://img.youtube.com/vi/zvzzA9GXu3Q/3.jpg" alt="zeppelin-view" hspace="10" width="200"></img>](https://www.youtube.com/watch?v=zvzzA9GXu3Q)
-
-* You can query on any arbitrary object
-* You can navigate object collections
-* You can invoke methods and access the behavior of objects
-* Data mapping is supported
-* You are not required to declare types. Since you do not need type definitions, you can work across multiple languages
-* You are not constrained by a schema
-
-This [Video Tutorial](https://www.youtube.com/watch?v=zvzzA9GXu3Q) illustrates some of the features provided by the `Geode Interpreter`.
-
-### Create Interpreter
-
-By default Zeppelin creates one `Geode/OQL` instance. You can remove it or create more instances.
-
-Multiple Geode instances can be created, each configured to the same or different backend Geode cluster. But over time a `Notebook` can have only one Geode interpreter instance `bound`. That means you _can not_ connect to different Geode clusters in the same `Notebook`. This is a known Zeppelin limitation.
-
-To create new Geode instance open the `Interprter` section and click the `+Create` button. Pick a `Name` of your choice and from the `Interpreter` drop-down select `geode`. Then follow the configuration instructions and `Save` the new instance.
-
-> Note: The `Name` of the instance is used only to distinct the instances while binding them to the `Notebook`. The `Name` is irrelevant inside the `Notebook`. In the `Notebook` you must use `%geode.oql` tag.
-
-### Bind to Notebook
-In the `Notebook` click on the `settings` icon in the top right corner. The select/deselect the interpreters to be bound with the `Notebook`.
-
-### Configuration
-You can modify the configuration of the Geode from the `Interpreter` section. The Geode interpreter express the following properties:
-
-
- <table class="table-configuration">
- <tr>
- <th>Property Name</th>
- <th>Description</th>
- <th>Default Value</th>
- </tr>
- <tr>
- <td>geode.locator.host</td>
- <td>The Geode Locator Host</td>
- <td>localhost</td>
- </tr>
- <tr>
- <td>geode.locator.port</td>
- <td>The Geode Locator Port</td>
- <td>10334</td>
- </tr>
- <tr>
- <td>geode.max.result</td>
- <td>Max number of OQL result to display to prevent the browser overload</td>
- <td>1000</td>
- </tr>
- </table>
-
-### How to use
-
-> *Tip 1: Use (CTRL + .) for OQL auto-completion.*
-
-> *Tip 2: Alawys start the paragraphs with the full `%geode.oql` prefix tag! The short notation: `%geode` would still be able run the OQL queries but the syntax highlighting and the auto-completions will be disabled.*
-
-#### Create / Destroy Regions
-
-The OQL sepecification does not support [Geode Regions](https://cwiki.apache.org/confluence/display/GEODE/Index#Index-MainConceptsandComponents) mutation operations. To `creaate`/`destroy` regions one should use the [GFSH](http://geode-docs.cfapps.io/docs/tools_modules/gfsh/chapter_overview.html) shell tool instead. To wokr this it assumes that the GFSH is colocated with Zeppelin server.
-
-```bash
-%sh
-source /etc/geode/conf/geode-env.sh
-gfsh << EOF
-
- connect --locator=ambari.localdomain[10334]
-
- destroy region --name=/regionEmployee
- destroy region --name=/regionCompany
- create region --name=regionEmployee --type=REPLICATE
- create region --name=regionCompany --type=REPLICATE
-
- exit;
-EOF
-```
-
-Above snippet re-creates two regions: `regionEmployee` and `regionCompany`. Note that you have to explicetely specify the locator host and port. The values should match those you have used in the Geode Interpreter configuration. Comprehensive list of [GFSH Commands by Functional Area](http://geode-docs.cfapps.io/docs/tools_modules/gfsh/gfsh_quick_reference.html).
-
-#### Basic OQL
-
-
-```sql
-%geode.oql
-SELECT count(*) FROM /regionEmploee
-```
-
-OQL `IN` and `SET` filters:
-
-```sql
-%geode.oql
-SELECT * FROM /regionEmployee
-WHERE companyId IN SET(2) OR lastName IN SET('Tzolov13', 'Tzolov73')
-```
-
-OQL `JOIN` operations
-
-```sql
-%geode.oql
-SELECT e.employeeId, e.firstName, e.lastName, c.id as companyId, c.companyName, c.address
-FROM /regionEmployee e, /regionCompany c
-WHERE e.companyId = c.id
-```
-
-By default the QOL responses contain only the region entry values. To access the keys, query the `EntrySet` instead:
-
-```sql
-%geode.oql
-SELECT e.key, e.value.companyId, e.value.email
-FROM /regionEmployee.entrySet e
-```
-Following query will return the EntrySet value as a Blob:
-
-```sql
-%geode.oql
-SELECT e.key, e.value FROM /regionEmployee.entrySet e
-```
-
-
-> Note: You can have multiple queries in the same paragraph but only the result from the first is displayed. [[1](https://issues.apache.org/jira/browse/ZEPPELIN-178)], [[2](https://issues.apache.org/jira/browse/ZEPPELIN-212)].
-
-
-#### GFSH Commands From The Shell
-
-Use the Shell Interpreter (`%sh`) to run OQL commands form the command line:
-
-```bash
-%sh
-source /etc/geode/conf/geode-env.sh
-gfsh -e "connect" -e "list members"
-```
-
-#### Apply Zeppelin Dynamic Forms
-
-You can leverage [Zepplein Dynamic Form](https://zeppelin.incubator.apache.org/docs/manual/dynamicform.html) inside your OQL queries. You can use both the `text input` and `select form` parametrization features
-
-```sql
-%geode.oql
-SELECT * FROM /regionEmployee e WHERE e.employeeId > ${Id}
-```
-
-#### Geode REST API
-To list the defined regions you can use the [Geode REST API](http://geode-docs.cfapps.io/docs/geode_rest/chapter_overview.html):
-
-```
-http://<geode server hostname>phd1.localdomain:8484/gemfire-api/v1/
-```
-
-```json
-{
- "regions" : [{
- "name" : "regionEmployee",
- "type" : "REPLICATE",
- "key-constraint" : null,
- "value-constraint" : null
- }, {
- "name" : "regionCompany",
- "type" : "REPLICATE",
- "key-constraint" : null,
- "value-constraint" : null
- }]
-}
-```
-
-> To enable Geode REST API with JSON support add the following properties to geode.server.properties.file and restart:
-
-```
-http-service-port=8484
-start-dev-rest-api=true
-```
-
-### Auto-completion
-The Geode Interpreter provides a basic auto-completion functionality. On `(Ctrl+.)` it list the most relevant suggesntions in a pop-up window.
-
-
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/interpreter/ignite.md
----------------------------------------------------------------------
diff --git a/docs/docs/interpreter/ignite.md b/docs/docs/interpreter/ignite.md
deleted file mode 100644
index 02fc587..0000000
--- a/docs/docs/interpreter/ignite.md
+++ /dev/null
@@ -1,116 +0,0 @@
----
-layout: page
-title: "Ignite Interpreter"
-description: "Ignite user guide"
-group: manual
----
-{% include JB/setup %}
-
-## Ignite Interpreter for Apache Zeppelin
-
-### Overview
-[Apache Ignite](https://ignite.apache.org/) In-Memory Data Fabric is a high-performance, integrated and distributed in-memory platform for computing and transacting on large-scale data sets in real-time, orders of magnitude faster than possible with traditional disk-based or flash technologies.
-
-
-
-You can use Zeppelin to retrieve distributed data from cache using Ignite SQL interpreter. Moreover, Ignite interpreter allows you to execute any Scala code in cases when SQL doesn't fit to your requirements. For example, you can populate data into your caches or execute distributed computations.
-
-### Installing and Running Ignite example
-In order to use Ignite interpreters, you may install Apache Ignite in some simple steps:
-
- 1. Download Ignite [source release](https://ignite.apache.org/download.html#sources) or [binary release](https://ignite.apache.org/download.html#binaries) whatever you want. But you must download Ignite as the same version of Zeppelin's. If it is not, you can't use scala code on Zeppelin. You can find ignite version in Zepplin at the pom.xml which is placed under `path/to/your-Zeppelin/ignite/pom.xml` ( Of course, in Zeppelin source release ). Please check `ignite.version` .<br>Currently, Zeppelin provides ignite only in Zeppelin source release. So, if you download Zeppelin binary release( `zeppelin-0.5.0-incubating-bin-spark-xxx-hadoop-xx` ), you can not use ignite interpreter on Zeppelin. We are planning to include ignite in a future binary release.
-
- 2. Examples are shipped as a separate Maven project, so to start running you simply need to import provided <dest_dir>/apache-ignite-fabric-1.2.0-incubating-bin/pom.xml file into your favourite IDE, such as Eclipse.
-
- * In case of Eclipse, Eclipse -> File -> Import -> Existing Maven Projects
- * Set examples directory path to Eclipse and select the pom.xml.
- * Then start `org.apache.ignite.examples.ExampleNodeStartup` (or whatever you want) to run at least one or more ignite node. When you run example code, you may notice that the number of node is increase one by one.
-
- > **Tip. If you want to run Ignite examples on the cli not IDE, you can export executable Jar file from IDE. Then run it by using below command.**
-
- ```
- $ nohup java -jar </path/to/your Jar file name>
- ```
-
-### Configuring Ignite Interpreter
-At the "Interpreters" menu, you may edit Ignite interpreter or create new one. Zeppelin provides these properties for Ignite.
-
- <table class="table-configuration">
- <tr>
- <th>Property Name</th>
- <th>value</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>ignite.addresses</td>
- <td>127.0.0.1:47500..47509</td>
- <td>Coma separated list of Ignite cluster hosts. See [Ignite Cluster Configuration](https://apacheignite.readme.io/v1.2/docs/cluster-config) section for more details.</td>
- </tr>
- <tr>
- <td>ignite.clientMode</td>
- <td>true</td>
- <td>You can connect to the Ignite cluster as client or server node. See [Ignite Clients vs. Servers](https://apacheignite.readme.io/v1.2/docs/clients-vs-servers) section for details. Use true or false values in order to connect in client or server mode respectively.</td>
- </tr>
- <tr>
- <td>ignite.config.url</td>
- <td></td>
- <td>Configuration URL. Overrides all other settings.</td>
- </tr
- <tr>
- <td>ignite.jdbc.url</td>
- <td>jdbc:ignite:cfg://default-ignite-jdbc.xml</td>
- <td>Ignite JDBC connection URL.</td>
- </tr>
- <tr>
- <td>ignite.peerClassLoadingEnabled</td>
- <td>true</td>
- <td>Enables peer-class-loading. See [Zero Deployment](https://apacheignite.readme.io/v1.2/docs/zero-deployment) section for details. Use true or false values in order to enable or disable P2P class loading respectively.</td>
- </tr>
- </table>
-
-
-
-### Interpreter Binding for Zeppelin Notebook
-After configuring Ignite interpreter, create your own notebook. Then you can bind interpreters like below image.
-
-
-
-For more interpreter binding information see [here](http://zeppelin.incubator.apache.org/docs/manual/interpreters.html).
-
-### How to use Ignite SQL interpreter
-In order to execute SQL query, use ` %ignite.ignitesql ` prefix. <br>
-Supposing you are running `org.apache.ignite.examples.streaming.wordcount.StreamWords`, then you can use "words" cache( Of course you have to specify this cache name to the Ignite interpreter setting section `ignite.jdbc.url` of Zeppelin ).
-For example, you can select top 10 words in the words cache using the following query
-
- ```
- %ignite.ignitesql
- select _val, count(_val) as cnt from String group by _val order by cnt desc limit 10
- ```
-
- 
-
-As long as your Ignite version and Zeppelin Ignite version is same, you can also use scala code. Please check the Zeppelin Ignite version before you download your own Ignite.
-
- ```
- %ignite
- import org.apache.ignite._
- import org.apache.ignite.cache.affinity._
- import org.apache.ignite.cache.query._
- import org.apache.ignite.configuration._
-
- import scala.collection.JavaConversions._
-
- val cache: IgniteCache[AffinityUuid, String] = ignite.cache("words")
-
- val qry = new SqlFieldsQuery("select avg(cnt), min(cnt), max(cnt) from (select count(_val) as cnt from String group by _val)", true)
-
- val res = cache.query(qry).getAll()
-
- collectionAsScalaIterable(res).foreach(println _)
- ```
-
- 
-
-Apache Ignite also provides a guide docs for Zeppelin ["Ignite with Apache Zeppelin"](https://apacheignite.readme.io/docs/data-analysis-with-apache-zeppelin)
-
-
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/interpreter/lens.md
----------------------------------------------------------------------
diff --git a/docs/docs/interpreter/lens.md b/docs/docs/interpreter/lens.md
deleted file mode 100644
index 903df7e..0000000
--- a/docs/docs/interpreter/lens.md
+++ /dev/null
@@ -1,173 +0,0 @@
----
-layout: page
-title: "Lens Interpreter"
-description: "Lens user guide"
-group: manual
----
-{% include JB/setup %}
-
-## Lens Interpreter for Apache Zeppelin
-
-### Overview
-[Apache Lens](https://lens.apache.org/) provides an Unified Analytics interface. Lens aims to cut the Data Analytics silos by providing a single view of data across multiple tiered data stores and optimal execution environment for the analytical query. It seamlessly integrates Hadoop with traditional data warehouses to appear like one.
-
-
-
-### Installing and Running Lens
-In order to use Lens interpreters, you may install Apache Lens in some simple steps:
-
- 1. Download Lens for latest version from [the ASF](http://www.apache.org/dyn/closer.lua/lens/2.3-beta). Or the older release can be found [in the Archives](http://archive.apache.org/dist/lens/).
- 2. Before running Lens, you have to set HIVE_HOME and HADOOP_HOME. If you want to get more information about this, please refer to [here](http://lens.apache.org/lenshome/install-and-run.html#Installation). Lens also provides Pseudo Distributed mode. [Lens pseudo-distributed setup](http://lens.apache.org/lenshome/pseudo-distributed-setup.html) is done by using [docker](https://www.docker.com/). Hive server and hadoop daemons are run as separate processes in lens pseudo-distributed setup.
- 3. Now, you can start lens server (or stop).
-
- ```
- ./bin/lens-ctl start (or stop)
- ```
-
-### Configuring Lens Interpreter
-At the "Interpreters" menu, you can to edit Lens interpreter or create new one. Zeppelin provides these properties for Lens.
-
- <table class="table-configuration">
- <tr>
- <th>Property Name</th>
- <th>value</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>lens.client.dbname</td>
- <td>default</td>
- <td>The database schema name</td>
- </tr>
- <tr>
- <td>lens.query.enable.persistent.resultset</td>
- <td>false</td>
- <td>Whether to enable persistent resultset for queries. When enabled, server will fetch results from driver, custom format them if any and store in a configured location. The file name of query output is queryhandle-id, with configured extensions</td>
- </tr>
- <tr>
- <td>lens.server.base.url</td>
- <td>http://hostname:port/lensapi</td>
- <td>The base url for the lens server. you have to edit "hostname" and "port" that you may use(ex. http://0.0.0.0:9999/lensapi)</td>
- </tr>
- <tr>
- <td>lens.session.cluster.user </td>
- <td>default</td>
- <td>Hadoop cluster username</td>
- </tr>
- <tr>
- <td>zeppelin.lens.maxResult</td>
- <td>1000</td>
- <td>Max number of rows to display</td>
- </tr>
- <tr>
- <td>zeppelin.lens.maxThreads</td>
- <td>10</td>
- <td>If concurrency is true then how many threads?</td>
- </tr>
- <tr>
- <td>zeppelin.lens.run.concurrent</td>
- <td>true</td>
- <td>Run concurrent Lens Sessions</td>
- </tr>
- <tr>
- <td>xxx</td>
- <td>yyy</td>
- <td>anything else from [Configuring lens server](https://lens.apache.org/admin/config-server.html)</td>
- </tr>
- </table>
-
-
-
-### Interpreter Bindging for Zeppelin Notebook
-After configuring Lens interpreter, create your own notebook, then you can bind interpreters like below image.
-
-
-For more interpreter binding information see [here](http://zeppelin.incubator.apache.org/docs/manual/interpreters.html).
-
-### How to use
-You can analyze your data by using [OLAP Cube](http://lens.apache.org/user/olap-cube.html) [QL](http://lens.apache.org/user/cli.html) which is a high level SQL like language to query and describe data sets organized in data cubes.
-You may experience OLAP Cube like this [Video tutorial](https://cwiki.apache.org/confluence/display/LENS/2015/07/13/20+Minute+video+demo+of+Apache+Lens+through+examples).
-As you can see in this video, they are using Lens Client Shell(./bin/lens-cli.sh). All of these functions also can be used on Zeppelin by using Lens interpreter.
-
-<li> Create and Use(Switch) Databases.
-
- ```
- create database newDb
- ```
-
- ```
- use newDb
- ```
-
-<li> Create Storage.
-
- ```
- create storage your/path/to/lens/client/examples/resources/db-storage.xml
- ```
-
-<li> Create Dimensions, Show fields and join-chains of them.
-
- ```
- create dimension your/path/to/lens/client/examples/resources/customer.xml
- ```
-
- ```
- dimension show fields customer
- ```
-
- ```
- dimension show joinchains customer
- ```
-
-<li> Create Caches, Show fields and join-chains of them.
-
- ```
- create cube your/path/to/lens/client/examples/resources/sales-cube.xml
- ```
-
- ```
- cube show fields sales
- ```
-
- ```
- cube show joinchains sales
- ```
-
-<li> Create Dimtables and Fact.
-
- ```
- create dimtable your/path/to/lens/client/examples/resources/customer_table.xml
- ```
-
- ```
- create fact your/path/to/lens/client/examples/resources/sales-raw-fact.xml
- ```
-
-<li> Add partitions to Dimtable and Fact.
-
- ```
- dimtable add single-partition --dimtable_name customer_table --storage_name local --path your/path/to/lens/client/examples/resources/customer-local-part.xml
- ```
-
- ```
- fact add partitions --fact_name sales_raw_fact --storage_name local --path your/path/to/lens/client/examples/resources/sales-raw-local-parts.xml
- ```
-
-<li> Now, you can run queries on cubes.
-
- ```
- query execute cube select customer_city_name, product_details.description, product_details.category, product_details.color, store_sales from sales where time_range_in(delivery_time, '2015-04-11-00', '2015-04-13-00')
- ```
-
-
- 
-
-These are just examples that provided in advance by Lens. If you want to explore whole tutorials of Lens, see the [tutorial video](https://cwiki.apache.org/confluence/display/LENS/2015/07/13/20+Minute+video+demo+of+Apache+Lens+through+examples).
-
-### Lens UI Service
-Lens also provides web UI service. Once the server starts up, you can open the service on http://serverhost:19999/index.html and browse. You may also check the structure that you made and use query easily here.
-
- 
-
-
-
-
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/interpreter/postgresql.md
----------------------------------------------------------------------
diff --git a/docs/docs/interpreter/postgresql.md b/docs/docs/interpreter/postgresql.md
deleted file mode 100644
index 9753cdc..0000000
--- a/docs/docs/interpreter/postgresql.md
+++ /dev/null
@@ -1,180 +0,0 @@
----
-layout: page
-title: "PostgreSQL and HAWQ Interpreter"
-description: ""
-group: manual
----
-{% include JB/setup %}
-
-
-## PostgreSQL, HAWQ Interpreter for Apache Zeppelin
-
-<br/>
-<table class="table-configuration">
- <tr>
- <th>Name</th>
- <th>Class</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>%psql.sql</td>
- <td>PostgreSqlInterpreter</td>
- <td>Provides SQL environment for Postgresql, HAWQ and Greenplum</td>
- </tr>
-</table>
-
-<br/>
-[<img align="right" src="http://img.youtube.com/vi/wqXXQhJ5Uk8/0.jpg" alt="zeppelin-view" hspace="10" width="250"></img>](https://www.youtube.com/watch?v=wqXXQhJ5Uk8)
-
-This interpreter seamlessly supports the following SQL data processing engines:
-
-* [PostgreSQL](http://www.postgresql.org/) - OSS, Object-relational database management system (ORDBMS)
-* [Apache HAWQ](http://pivotal.io/big-data/pivotal-hawq) - Powerful [Open Source](https://wiki.apache.org/incubator/HAWQProposal) SQL-On-Hadoop engine.
-* [Greenplum](http://pivotal.io/big-data/pivotal-greenplum-database) - MPP database built on open source PostgreSQL.
-
-
-This [Video Tutorial](https://www.youtube.com/watch?v=wqXXQhJ5Uk8) illustrates some of the features provided by the `Postgresql Interpreter`.
-
-### Create Interpreter
-
-By default Zeppelin creates one `PSQL` instance. You can remove it or create new instances.
-
-Multiple PSQL instances can be created, each configured to the same or different backend databases. But over time a `Notebook` can have only one PSQL interpreter instance `bound`. That means you _can not_ connect to different databases in the same `Notebook`. This is a known Zeppelin limitation.
-
-To create new PSQL instance open the `Interprter` section and click the `+Create` button. Pick a `Name` of your choice and from the `Interpreter` drop-down select `psql`. Then follow the configuration instructions and `Save` the new instance.
-
-> Note: The `Name` of the instance is used only to distinct the instances while binding them to the `Notebook`. The `Name` is irrelevant inside the `Notebook`. In the `Notebook` you must use `%psql.sql` tag.
-
-### Bind to Notebook
-In the `Notebook` click on the `settings` icon in the top right corner. The select/deselect the interpreters to be bound with the `Notebook`.
-
-### Configuration
-You can modify the configuration of the PSQL from the `Interpreter` section. The PSQL interpreter expenses the following properties:
-
-
- <table class="table-configuration">
- <tr>
- <th>Property Name</th>
- <th>Description</th>
- <th>Default Value</th>
- </tr>
- <tr>
- <td>postgresql.url</td>
- <td>JDBC URL to connect to </td>
- <td>jdbc:postgresql://localhost:5432</td>
- </tr>
- <tr>
- <td>postgresql.user</td>
- <td>JDBC user name</td>
- <td>gpadmin</td>
- </tr>
- <tr>
- <td>postgresql.password</td>
- <td>JDBC password</td>
- <td></td>
- </tr>
- <tr>
- <td>postgresql.driver.name</td>
- <td>JDBC driver name. In this version the driver name is fixed and should not be changed</td>
- <td>org.postgresql.Driver</td>
- </tr>
- <tr>
- <td>postgresql.max.result</td>
- <td>Max number of SQL result to display to prevent the browser overload</td>
- <td>1000</td>
- </tr>
- </table>
-
-
-### How to use
-```
-Tip: Use (CTRL + .) for SQL auto-completion.
-```
-#### DDL and SQL commands
-
-Start the paragraphs with the full `%psql.sql` prefix tag! The short notation: `%psql` would still be able run the queries but the syntax highlighting and the auto-completions will be disabled.
-
-You can use the standard CREATE / DROP / INSERT commands to create or modify the data model:
-
-```sql
-%psql.sql
-drop table if exists mytable;
-create table mytable (i int);
-insert into mytable select generate_series(1, 100);
-```
-
-Then in a separate paragraph run the query.
-
-```sql
-%psql.sql
-select * from mytable;
-```
-
-> Note: You can have multiple queries in the same paragraph but only the result from the first is displayed. [[1](https://issues.apache.org/jira/browse/ZEPPELIN-178)], [[2](https://issues.apache.org/jira/browse/ZEPPELIN-212)].
-
-For example, this will execute both queries but only the count result will be displayed. If you revert the order of the queries the mytable content will be shown instead.
-
-```sql
-%psql.sql
-select count(*) from mytable;
-select * from mytable;
-```
-
-#### PSQL command line tools
-
-Use the Shell Interpreter (`%sh`) to access the command line [PSQL](http://www.postgresql.org/docs/9.4/static/app-psql.html) interactively:
-
-```bash
-%sh
-psql -h phd3.localdomain -U gpadmin -p 5432 <<EOF
- \dn
- \q
-EOF
-```
-This will produce output like this:
-
-```
- Name | Owner
---------------------+---------
- hawq_toolkit | gpadmin
- information_schema | gpadmin
- madlib | gpadmin
- pg_catalog | gpadmin
- pg_toast | gpadmin
- public | gpadmin
- retail_demo | gpadmin
-```
-
-#### Apply Zeppelin Dynamic Forms
-
-You can leverage [Zepplein Dynamic Form](https://zeppelin.incubator.apache.org/docs/manual/dynamicform.html) inside your queries. You can use both the `text input` and `select form` parametrization features
-
-```sql
-%psql.sql
-SELECT ${group_by}, count(*) as count
-FROM retail_demo.order_lineitems_pxf
-GROUP BY ${group_by=product_id,product_id|product_name|customer_id|store_id}
-ORDER BY count ${order=DESC,DESC|ASC}
-LIMIT ${limit=10};
-```
-#### Example HAWQ PXF/HDFS Tables
-
-Create HAWQ external table that read data from tab-separated-value data in HDFS.
-
-```sql
-%psql.sql
-CREATE EXTERNAL TABLE retail_demo.payment_methods_pxf (
- payment_method_id smallint,
- payment_method_code character varying(20)
-) LOCATION ('pxf://${NAME_NODE_HOST}:50070/retail_demo/payment_methods.tsv.gz?profile=HdfsTextSimple') FORMAT 'TEXT' (DELIMITER = E'\t');
-```
-And retrieve content
-
-```sql
-%psql.sql
-seelect * from retail_demo.payment_methods_pxf
-```
-### Auto-completion
-The PSQL Interpreter provides a basic auto-completion functionality. On `(Ctrl+.)` it list the most relevant suggesntions in a pop-up window. In addition to the SQL keyword the interpter provides suggestions for the Schema, Table, Column names as well.
-
-
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/interpreter/spark.md
----------------------------------------------------------------------
diff --git a/docs/docs/interpreter/spark.md b/docs/docs/interpreter/spark.md
deleted file mode 100644
index 58fce0b..0000000
--- a/docs/docs/interpreter/spark.md
+++ /dev/null
@@ -1,221 +0,0 @@
----
-layout: page
-title: "Spark Interpreter Group"
-description: ""
-group: manual
----
-{% include JB/setup %}
-
-
-## Spark
-
-[Apache Spark](http://spark.apache.org) is supported in Zeppelin with
-Spark Interpreter group, which consisted of 4 interpreters.
-
-<table class="table-configuration">
- <tr>
- <th>Name</th>
- <th>Class</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>%spark</td>
- <td>SparkInterpreter</td>
- <td>Creates SparkContext and provides scala environment</td>
- </tr>
- <tr>
- <td>%pyspark</td>
- <td>PySparkInterpreter</td>
- <td>Provides python environment</td>
- </tr>
- <tr>
- <td>%sql</td>
- <td>SparkSQLInterpreter</td>
- <td>Provides SQL environment</td>
- </tr>
- <tr>
- <td>%dep</td>
- <td>DepInterpreter</td>
- <td>Dependency loader</td>
- </tr>
-</table>
-
-
-<br />
-
-
-### SparkContext, SQLContext, ZeppelinContext
-
-SparkContext, SQLContext, ZeppelinContext are automatically created and exposed as variable names 'sc', 'sqlContext' and 'z', respectively, both in scala and python environments.
-
-Note that scala / python environment shares the same SparkContext, SQLContext, ZeppelinContext instance.
-
-
-<a name="dependencyloading"> </a>
-<br />
-<br />
-### Dependency Management
-There are two ways to load external library in spark interpreter. First is using Zeppelin's %dep interpreter and second is loading Spark properties.
-
-#### 1. Dynamic Dependency Loading via %dep interpreter
-
-When your code requires external library, instead of doing download/copy/restart Zeppelin, you can easily do following jobs using %dep interpreter.
-
- * Load libraries recursively from Maven repository
- * Load libraries from local filesystem
- * Add additional maven repository
- * Automatically add libraries to SparkCluster (You can turn off)
-
-Dep interpreter leverages scala environment. So you can write any Scala code here.
-Note that %dep interpreter should be used before %spark, %pyspark, %sql.
-
-Here's usages.
-
-```scala
-%dep
-z.reset() // clean up previously added artifact and repository
-
-// add maven repository
-z.addRepo("RepoName").url("RepoURL")
-
-// add maven snapshot repository
-z.addRepo("RepoName").url("RepoURL").snapshot()
-
-// add credentials for private maven repository
-z.addRepo("RepoName").url("RepoURL").username("username").password("password")
-
-// add artifact from filesystem
-z.load("/path/to.jar")
-
-// add artifact from maven repository, with no dependency
-z.load("groupId:artifactId:version").excludeAll()
-
-// add artifact recursively
-z.load("groupId:artifactId:version")
-
-// add artifact recursively except comma separated GroupID:ArtifactId list
-z.load("groupId:artifactId:version").exclude("groupId:artifactId,groupId:artifactId, ...")
-
-// exclude with pattern
-z.load("groupId:artifactId:version").exclude(*)
-z.load("groupId:artifactId:version").exclude("groupId:artifactId:*")
-z.load("groupId:artifactId:version").exclude("groupId:*")
-
-// local() skips adding artifact to spark clusters (skipping sc.addJar())
-z.load("groupId:artifactId:version").local()
-```
-
-
-<br />
-#### 2. Loading Spark Properties
-Once `SPARK_HOME` is set in `conf/zeppelin-env.sh`, Zeppelin uses `spark-submit` as spark interpreter runner. `spark-submit` supports two ways to load configurations. The first is command line options such as --master and Zeppelin can pass these options to `spark-submit` by exporting `SPARK_SUBMIT_OPTIONS` in conf/zeppelin-env.sh. Second is reading configuration options from `SPARK_HOME/conf/spark-defaults.conf`. Spark properites that user can set to distribute libraries are:
-
-<table class="table-configuration">
- <tr>
- <th>spark-defaults.conf</th>
- <th>SPARK_SUBMIT_OPTIONS</th>
- <th>Applicable Interpreter</th>
- <th>Description</th>
- </tr>
- <tr>
- <td>spark.jars</td>
- <td>--jars</td>
- <td>%spark</td>
- <td>Comma-separated list of local jars to include on the driver and executor classpaths.</td>
- </tr>
- <tr>
- <td>spark.jars.packages</td>
- <td>--packages</td>
- <td>%spark</td>
- <td>Comma-separated list of maven coordinates of jars to include on the driver and executor classpaths. Will search the local maven repo, then maven central and any additional remote repositories given by --repositories. The format for the coordinates should be groupId:artifactId:version.</td>
- </tr>
- <tr>
- <td>spark.files</td>
- <td>--files</td>
- <td>%pyspark</td>
- <td>Comma-separated list of files to be placed in the working directory of each executor.</td>
- </tr>
-</table>
-Note that adding jar to pyspark is only availabe via %dep interpreter at the moment
-
-<br/>
-Here are few examples:
-
-##### 0.5.5 and later
-* SPARK\_SUBMIT\_OPTIONS in conf/zeppelin-env.sh
-
- export SPARK_SUBMIT_OPTIONS="--packages com.databricks:spark-csv_2.10:1.2.0 --jars /path/mylib1.jar,/path/mylib2.jar --files /path/mylib1.py,/path/mylib2.zip,/path/mylib3.egg"
-
-* SPARK_HOME/conf/spark-defaults.conf
-
- spark.jars /path/mylib1.jar,/path/mylib2.jar
- spark.jars.packages com.databricks:spark-csv_2.10:1.2.0
- spark.files /path/mylib1.py,/path/mylib2.egg,/path/mylib3.zip
-
-##### 0.5.0
-* ZEPPELIN\_JAVA\_OPTS in conf/zeppelin-env.sh
-
- export ZEPPELIN_JAVA_OPTS="-Dspark.jars=/path/mylib1.jar,/path/mylib2.jar -Dspark.files=/path/myfile1.dat,/path/myfile2.dat"
-<br />
-
-
-<a name="zeppelincontext"> </a>
-<br />
-<br />
-### ZeppelinContext
-
-
-Zeppelin automatically injects ZeppelinContext as variable 'z' in your scala/python environment. ZeppelinContext provides some additional functions and utility.
-
-<br />
-#### Object exchange
-
-ZeppelinContext extends map and it's shared between scala, python environment.
-So you can put some object from scala and read it from python, vise versa.
-
-Put object from scala
-
-```scala
-%spark
-val myObject = ...
-z.put("objName", myObject)
-```
-
-Get object from python
-
-```python
-%python
-myObject = z.get("objName")
-```
-
-<br />
-#### Form creation
-
-ZeppelinContext provides functions for creating forms.
-In scala and python environments, you can create forms programmatically.
-
-```scala
-%spark
-/* Create text input form */
-z.input("formName")
-
-/* Create text input form with default value */
-z.input("formName", "defaultValue")
-
-/* Create select form */
-z.select("formName", Seq(("option1", "option1DisplayName"),
- ("option2", "option2DisplayName")))
-
-/* Create select form with default value*/
-z.select("formName", "option1", Seq(("option1", "option1DisplayName"),
- ("option2", "option2DisplayName")))
-```
-
-In sql environment, you can create form in simple template.
-
-```
-%sql
-select * from ${table=defaultTableName} where text like '%${search}%'
-```
-
-To learn more about dynamic form, checkout [Dynamic Form](../dynamicform.html).
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/manual/dynamicform.md
----------------------------------------------------------------------
diff --git a/docs/docs/manual/dynamicform.md b/docs/docs/manual/dynamicform.md
deleted file mode 100644
index 06074fd..0000000
--- a/docs/docs/manual/dynamicform.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-layout: page
-title: "Dynamic Form"
-description: ""
-group: manual
----
-<!--
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-{% include JB/setup %}
-
-
-## Dynamic Form
-
-Zeppelin dynamically creates input forms. Depending on language backend, there're two different ways to create dynamic form.
-Custom language backend can select which type of form creation it wants to use.
-
-<br />
-### Using form Templates
-
-This mode creates form using simple template language. It's simple and easy to use. For example Markdown, Shell, SparkSql language backend uses it.
-
-<br />
-#### Text input form
-
-To create text input form, use _${formName}_ templates.
-
-for example
-
-<img src="../../assets/themes/zeppelin/img/screenshots/form_input.png" />
-
-
-Also you can provide default value, using _${formName=defaultValue}_.
-
-<img src="../../assets/themes/zeppelin/img/screenshots/form_input_default.png" />
-
-
-<br />
-#### Select form
-
-To create select form, use _${formName=defaultValue,option1|option2...}_
-
-for example
-
-<img src="../../assets/themes/zeppelin/img/screenshots/form_select.png" />
-
-Also you can separate option's display name and value, using _${formName=defaultValue,option1(DisplayName)|option2(DisplayName)...}_
-
-<img src="../../assets/themes/zeppelin/img/screenshots/form_select_displayname.png" />
-
-<br />
-### Creates Programmatically
-
-Some language backend uses programmatic way to create form. For example [ZeppelinContext](./interpreter/spark.html#zeppelincontext) provides form creation API
-
-Here're some examples.
-
-Text input form
-
-<img src="../../assets/themes/zeppelin/img/screenshots/form_input_prog.png" />
-
-Text input form with default value
-
-<img src="../../assets/themes/zeppelin/img/screenshots/form_input_default_prog.png" />
-
-Select form
-
-<img src="../../assets/themes/zeppelin/img/screenshots/form_select_prog.png" />
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/manual/interpreters.md
----------------------------------------------------------------------
diff --git a/docs/docs/manual/interpreters.md b/docs/docs/manual/interpreters.md
deleted file mode 100644
index ff5bff7..0000000
--- a/docs/docs/manual/interpreters.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-layout: page
-title: "Interpreters"
-description: ""
-group: manual
----
-<!--
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-{% include JB/setup %}
-
-
-## Interpreters in zeppelin
-
-This section explain the role of Interpreters, interpreters group and interpreters settings in Zeppelin.
-Zeppelin interpreter concept allows any language/data-processing-backend to be plugged into Zeppelin.
-Currently Zeppelin supports many interpreters such as Scala(with Apache Spark), Python(with Apache Spark), SparkSQL, Hive, Markdown and Shell.
-
-### What is zeppelin interpreter?
-
-Zeppelin Interpreter is the plug-in which enable zeppelin user to use a specific language/data-processing-backend. For example to use scala code in Zeppelin, you need ```spark``` interpreter.
-
-When you click on the ```+Create``` button in the interpreter page the interpreter drop-down list box will present all the available interpreters on your server.
-
-<img src="../../assets/themes/zeppelin/img/screenshots/interpreter_create.png">
-
-### What is zeppelin interpreter setting?
-
-Zeppelin interpreter setting is the configuration of a given interpreter on zeppelin server. For example, the properties requried for hive JDBC interpreter to connect to the Hive server.
-
-<img src="../../assets/themes/zeppelin/img/screenshots/interpreter_setting.png">
-### What is zeppelin interpreter group?
-
-Every Interpreter belongs to an InterpreterGroup. InterpreterGroup is a unit of start/stop interpreter.
-By default, every interpreter belong to a single group but the group might contain more interpreters. For example, spark interpreter group include spark support, pySpark,
-SparkSQL and the dependency loader.
-
-Technically, Zeppelin interpreters from the same group are running in the same JVM.
-
-Interpreters belong to a single group a registered together and all of their properties are listed in the interpreter setting.
-<img src="../../assets/themes/zeppelin/img/screenshots/interpreter_setting_spark.png">
-
-### Programming langages for interpreter
-
-If the interpreter uses a specific programming language (like Scala, Python, SQL), it is generally a good idea to add syntax highlighting support for that to the notebook paragraph editor.
-
-To check out the list of languages supported, see the mode-*.js files under zeppelin-web/bower_components/ace-builds/src-noconflict or from github https://github.com/ajaxorg/ace-builds/tree/master/src-noconflict
-
-To add a new set of syntax highlighting,
-1. add the mode-*.js file to zeppelin-web/bower.json (when built, zeppelin-web/src/index.html will be changed automatically)
-2. add to the list of `editorMode` in zeppelin-web/src/app/notebook/paragraph/paragraph.controller.js - it follows the pattern 'ace/mode/x' where x is the name
-3. add to the code that checks for `%` prefix and calls `session.setMode(editorMode.x)` in `setParagraphMode` in zeppelin-web/src/app/notebook/paragraph/paragraph.controller.js
-
-
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/manual/notebookashomepage.md
----------------------------------------------------------------------
diff --git a/docs/docs/manual/notebookashomepage.md b/docs/docs/manual/notebookashomepage.md
deleted file mode 100644
index 86f1ea9..0000000
--- a/docs/docs/manual/notebookashomepage.md
+++ /dev/null
@@ -1,109 +0,0 @@
----
-layout: page
-title: "Notebook as Homepage"
-description: ""
-group: manual
----
-<!--
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-{% include JB/setup %}
-
-## Customize your zeppelin homepage
- Zeppelin allows you to use one of the notebooks you create as your zeppelin Homepage.
- With that you can brand your zeppelin installation,
- adjust the instruction to your users needs and even translate to other languages.
-
- <br />
-### How to set a notebook as your zeppelin homepage
-
-The process for creating your homepage is very simple as shown below:
-
- 1. Create a notebook using zeppelin
- 2. Set the notebook id in the config file
- 3. Restart zeppelin
-
- <br />
-#### Create a notebook using zeppelin
- Create a new notebook using zeppelin,
- you can use ```%md``` interpreter for markdown content or any other interpreter you like.
-
- You can also use the display system to generate [text](../displaysystem/display.html),
- [html](../displaysystem/display.html#html),[table](../displaysystem/table.html) or
- [angular](../displaysystem/angular.html)
-
- Run (shift+Enter) the notebook and see the output. Optionally, change the notebook view to report to hide
- the code sections.
-
- <br />
-#### Set the notebook id in the config file
- To set the notebook id in the config file you should copy it from the last word in the notebook url
-
- for example
-
- <img src="../../assets/themes/zeppelin/img/screenshots/homepage_notebook_id.png" />
-
- Set the notebook id to the ```ZEPPELIN_NOTEBOOK_HOMESCREEN``` environment variable
- or ```zeppelin.notebook.homescreen``` property.
-
- You can also set the ```ZEPPELIN_NOTEBOOK_HOMESCREEN_HIDE``` environment variable
- or ```zeppelin.notebook.homescreen.hide``` property to hide the new notebook from the notebook list.
-
- <br />
-#### Restart zeppelin
- Restart your zeppelin server
-
- ```
- ./bin/zeppelin-deamon stop
- ./bin/zeppelin-deamon start
- ```
- ####That's it! Open your browser and navigate to zeppelin and see your customized homepage...
-
-
-<br />
-### Show notebooks list in your custom homepage
-If you want to display the list of notebooks on your custom zeppelin homepage all
-you need to do is use our %angular support.
-
- <br />
- Add the following code to a paragraph in you home page and run it... walla! you have your notebooks list.
-
- ```javascript
- println(
- """%angular
- <div class="col-md-4" ng-controller="HomeCtrl as home">
- <h4>Notebooks</h4>
- <div>
- <h5><a href="" data-toggle="modal" data-target="#noteNameModal" style="text-decoration: none;">
- <i style="font-size: 15px;" class="icon-notebook"></i> Create new note</a></h5>
- <ul style="list-style-type: none;">
- <li ng-repeat="note in home.notes.list track by $index"><i style="font-size: 10px;" class="icon-doc"></i>
- <a style="text-decoration: none;" href="#/notebook/{{note.id}}">{{note.name || 'Note ' + note.id}}</a>
- </li>
- </ul>
- </div>
- </div>
- """)
- ```
-
- After running the notebook you will see output similar to this one:
- <img src="../../assets/themes/zeppelin/img/screenshots/homepage_notebook_list.png" />
-
- The main trick here relays in linking the ```<div>``` to the controller:
-
- ```javascript
- <div class="col-md-4" ng-controller="HomeCtrl as home">
- ```
-
- Once we have ```home``` as our controller variable in our ```<div></div>```
- we can use ```home.notes.list``` to get access to the notebook list.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/pleasecontribute.md
----------------------------------------------------------------------
diff --git a/docs/docs/pleasecontribute.md b/docs/docs/pleasecontribute.md
deleted file mode 100644
index 063b48f..0000000
--- a/docs/docs/pleasecontribute.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-layout: page
-title: "Please contribute"
-description: ""
-group: development
----
-<!--
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-{% include JB/setup %}
-
-
-### Waiting for your help
-The content does not exist yet.
-
-We're always welcoming contribution.
-
-If you're interested, please check [How to contribute (website)](./development/howtocontributewebsite.html).
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/c2cbafd1/docs/docs/releases/zeppelin-release-0.5.0-incubating.md
----------------------------------------------------------------------
diff --git a/docs/docs/releases/zeppelin-release-0.5.0-incubating.md b/docs/docs/releases/zeppelin-release-0.5.0-incubating.md
deleted file mode 100644
index a6fbe4d..0000000
--- a/docs/docs/releases/zeppelin-release-0.5.0-incubating.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-layout: page
-title: "Zeppelin Release 0.5.0-incubating"
-description: ""
-group: release
----
-<!--
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-{% include JB/setup %}
-
-### Zeppelin Release 0.5.0-incubating
-
-Zeppelin 0.5.0-incubating is the first release under Apache incubation, with contributions from 42 developers and more than 600 commits.
-
-To download Zeppelin 0.5.0-incubating visit the [download](../../download.html) page.
-
-You can visit [issue tracker](https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221&version=12329850) for full list of issues being resolved.
-
-### Contributors
-
-The following developers contributed to this release:
-
-* Akshat Aranya - New features and Improvements in UI.
-* Alexander Bezzubov -Improvements and Bug fixes in Core, UI, Build system. New feature and Improvements in Spark interpreter. Documentation in roadmap.
-* Anthony Corbacho - Improvements in Website. Bug fixes Build system. Improvements and Bug fixes in UI. Documentation in roadmap.
-* Brennon York - Improvements and Bug fixes in Build system.
-* CORNEAU Damien - New feature, Improvements and Bug fixes in UI and Build system.
-* Corey Huang - Improvements in Build system. New feature in Core.
-* Digeratus - Improvements in Tutorials.
-* Dimitrios Liapis - Improvements in Documentation.
-* DuyHai DOAN - New feature in Build system.
-* Emmanuelle Raffenne - Bug fixes in UI.
-* Eran Medan - Improvements in Documentation.
-* Eugene Morozov - Bug fixes in Core.
-* Felix Cheung - Improvements in Spark interpreter. Improvements in Documentation. New features, Improvements and Bug fixes in UI.
-* Hung Lin - Improvements in Core.
-* Hyungu Roh - Bug fixes in UI.
-* Ilya Ganelin - Improvements in Tutorials.
-* JaeHwa Jung - New features in Tajo interpreter.
-* Jakob Homan - Improvements in Website.
-* James Carman - Improvements in Build system.
-* Jongyoul Lee - Improvements in Core, Build system and Spark interpreter. Bug fixes in Spark Interpreter. New features in Build system and Spark interpreter. Improvements in Documentation.
-* Juarez Bochi - Bug fixes in Build system.
-* Julien Buret - Bug fixes in Spark interpreter.
-* Jérémy Subtil - Bug fixes in Build system.
-* Kevin (SangWoo) Kim - New features in Core, Tutorials. Improvements in Documentation. New features, Improvements and Bug fixes in UI.
-* Kyoung-chan Lee - Improvements in Documentation.
-* Lee moon soo - Improvements in Tutorials. New features, Improvements and Bug fixes in Core, UI, Build system and Spark interpreter. New features in Flink interpreter. Improvments in Documentation.
-* Mina Lee - Improvements and Bug fixes in UI. New features in UI. Improvements in Core, Website.
-* Rajat Gupta - Bug fixes in Spark interpreter.
-* Ram Venkatesh - Improvements in Core, Build system, Spark interpreter and Markdown interpreter. New features and Bug fixes in Hive interpreter.
-* Sebastian YEPES - Improvements in Core.
-* Seckin Savasci - Improvements in Build system.
-* Timothy Shelton - Bug fixes in UI.
-* Vincent Botta - New features in UI.
-* Young boom - Improvements in UI.
-* bobbych - Improvements in Spark interpreter.
-* debugger87 - Bug fixes in Core.
-* dobachi - Improvements in UI.
-* epahomov - Improvements in Core and Spark interpreter.
-* kevindai0126 - Improvements in Core.
-* rahul agarwal - Bug fixes in Core.
-* whisperstream - Improvements in Spark interpreter.
-* yundai - Improvements in Core.
-
-Thanks to everyone who made this release possible!