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 2016/01/21 03:21:14 UTC
[1/2] incubator-zeppelin git commit: Fix styles of documentation
about interpreters
Repository: incubator-zeppelin
Updated Branches:
refs/heads/master dcda63eb2 -> 0d157aebd
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d157aeb/docs/interpreter/spark.md
----------------------------------------------------------------------
diff --git a/docs/interpreter/spark.md b/docs/interpreter/spark.md
index 87eaac1..6141619 100644
--- a/docs/interpreter/spark.md
+++ b/docs/interpreter/spark.md
@@ -8,7 +8,6 @@ group: manual
## Spark Interpreter for Apache Zeppelin
-
[Apache Spark](http://spark.apache.org) is supported in Zeppelin with
Spark Interpreter group, which consisted of 4 interpreters.
@@ -40,14 +39,10 @@ Spark Interpreter group, which consisted of 4 interpreters.
</tr>
</table>
-<br />
## Configuration
-
Without any configuration, Spark interpreter works out of box in local mode. But if you want to connect to your Spark cluster, you'll need to follow below two simple steps.
-
### 1. Export SPARK_HOME
-
In **conf/zeppelin-env.sh**, export `SPARK_HOME` environment variable with your Spark installation path.
for example
@@ -64,7 +59,6 @@ export SPARK_SUBMIT_OPTIONS="--packages com.databricks:spark-csv_2.10:1.2.0"
```
### 2. Set master in Interpreter menu
-
After start Zeppelin, go to **Interpreter** menu and edit **master** property in your Spark interpreter setting. The value may vary depending on your Spark cluster deployment type.
for example,
@@ -74,25 +68,21 @@ for example,
* **yarn-client** in Yarn client mode
* **mesos://host:5050** in Mesos cluster
-
-
That's it. Zeppelin will work with any version of Spark and any deployment type without rebuilding Zeppelin in this way. ( Zeppelin 0.5.5-incubating release works up to Spark 1.5.2 )
> Note that without exporting `SPARK_HOME`, it's running in local mode with included version of Spark. The included version may vary depending on the build profile.
-<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.
-<br />
<a name="dependencyloading"> </a>
+
## 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
@@ -182,15 +172,13 @@ Here are few examples:
spark.jars.packages com.databricks:spark-csv_2.10:1.2.0
spark.files /path/mylib1.py,/path/mylib2.egg,/path/mylib3.zip
-<br />
## ZeppelinContext
-
Zeppelin automatically injects ZeppelinContext as variable 'z' in your scala/python environment. ZeppelinContext provides some additional functions and utility.
### 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.
+
<div class="codetabs">
<div data-lang="scala" markdown="1">
@@ -212,6 +200,7 @@ myObject = z.get("objName")
</div>
</div>
+
### Form Creation
ZeppelinContext provides functions for creating forms.
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d157aeb/docs/manual/interpreters.md
----------------------------------------------------------------------
diff --git a/docs/manual/interpreters.md b/docs/manual/interpreters.md
index fd4c2bc..c886718 100644
--- a/docs/manual/interpreters.md
+++ b/docs/manual/interpreters.md
@@ -19,31 +19,24 @@ limitations under the License.
-->
{% include JB/setup %}
-
## Interpreters in Zeppelin
In this section, we will explain about the role of interpreters, interpreters group and interpreter settings in Zeppelin.
The concept of Zeppelin interpreter 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, Shell and so on.
-<br/>
## What is Zeppelin interpreter?
-
Zeppelin Interpreter is a plug-in which enables Zeppelin users to use a specific language/data-processing-backend. For example, to use scala code in Zeppelin, you need `%spark` interpreter.
When you click the ```+Create``` button in the interpreter page, the interpreter drop-down list box will show all the available interpreters on your server.
<img src="/assets/themes/zeppelin/img/screenshots/interpreter_create.png">
-<br/>
## What is Zeppelin Interpreter Setting?
-
Zeppelin interpreter setting is the configuration of a given interpreter on Zeppelin server. For example, the properties are required for hive JDBC interpreter to connect to the Hive server.
<img src="/assets/themes/zeppelin/img/screenshots/interpreter_setting.png">
-<br/>
## What is Zeppelin Interpreter Group?
-
Every Interpreter is belonged to an **Interpreter Group**. Interpreter Group is a unit of start/stop interpreter.
By default, every interpreter is belonged to a single group, but the group might contain more interpreters. For example, spark interpreter group is including Spark support, pySpark,
SparkSQL and the dependency loader.
@@ -53,9 +46,7 @@ Technically, Zeppelin interpreters from the same group are running in the same J
Each interpreters is belonged to a single group and registered together. All of their properties are listed in the interpreter setting like below image.
<img src="/assets/themes/zeppelin/img/screenshots/interpreter_setting_spark.png">
-<br/>
## Programming Languages for Interpreter
-
If the interpreter uses a specific programming language ( like Scala, Python, SQL ), it is generally recommended to add a syntax highlighting supported 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.com/ajaxorg/ace-builds](https://github.com/ajaxorg/ace-builds/tree/master/src-noconflict).
@@ -65,5 +56,3 @@ If you want 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` located in `zeppelin-web/src/app/notebook/paragraph/paragraph.controller.js`.
-
-
[2/2] incubator-zeppelin git commit: Fix styles of documentation
about interpreters
Posted by mo...@apache.org.
Fix styles of documentation about interpreters
Due to the documentation of interpreters written by various authors, styles of documentations are vary and has broken tags and inconsistent spaces. This fix cleans those little glitches to make documentation more readable and look cleaner to users.
1) Clean up unnecessary or wrong HTML tags ex: \<hr/\> after titles
2) Fix too wide spaces between paragraph and tables
3) Remove unnecessary spaces at end of paragraph and lines
Author: Jesang Yoon <yo...@kanizsalab.com>
Closes #648 from yoonjs2/master and squashes the following commits:
eba0315 [Jesang Yoon] Merge remote-tracking branch 'upstream/master'
db8b4da [Jesang Yoon] Merge remote-tracking branch 'upstream/master'
781954b [Jesang Yoon] Interpreter documentation merge with commit #578
af55811 [Jesang Yoon] Merge remote-tracking branch 'origin/master'
079480f [Jesang Yoon] Merge remote-tracking branch 'origin/master'
5f0a6e0 [Jesang Yoon] Merge remote-tracking branch 'origin/master'
4d1503a [Jesang Yoon] Merge remote-tracking branch 'origin/master'
5b091e4 [Jesang Yoon] Fix wrong HTML tags, indention and space between paragraph and tables. Remove unnecessary spaces.
5665dcf [Jesang Yoon] Fix wrong HTML tags, indention and space between paragraph and tables. Remove unnecessary spaces.
Project: http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/commit/0d157aeb
Tree: http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/tree/0d157aeb
Diff: http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/diff/0d157aeb
Branch: refs/heads/master
Commit: 0d157aebd2199cc6badc36810fd4518fa539d6c4
Parents: dcda63e
Author: Jesang Yoon <yo...@kanizsalab.com>
Authored: Tue Jan 19 10:57:24 2016 +0900
Committer: Lee moon soo <mo...@apache.org>
Committed: Wed Jan 20 18:23:42 2016 -0800
----------------------------------------------------------------------
docs/interpreter/cassandra.md | 979 ++++++++++++++++-----------------
docs/interpreter/elasticsearch.md | 105 ++--
docs/interpreter/flink.md | 4 -
docs/interpreter/geode.md | 60 +-
docs/interpreter/hive.md | 8 +-
docs/interpreter/ignite.md | 121 ++--
docs/interpreter/lens.md | 194 ++++---
docs/interpreter/postgresql.md | 81 ++-
docs/interpreter/scalding.md | 17 +-
docs/interpreter/spark.md | 17 +-
docs/manual/interpreters.md | 11 -
11 files changed, 736 insertions(+), 861 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d157aeb/docs/interpreter/cassandra.md
----------------------------------------------------------------------
diff --git a/docs/interpreter/cassandra.md b/docs/interpreter/cassandra.md
index 2eb86c3..3cec02d 100644
--- a/docs/interpreter/cassandra.md
+++ b/docs/interpreter/cassandra.md
@@ -6,8 +6,7 @@ group: manual
---
{% include JB/setup %}
-## 1. Cassandra CQL Interpreter for Apache Zeppelin
-
+## Cassandra CQL Interpreter for Apache Zeppelin
<table class="table-configuration">
<tr>
<th>Name</th>
@@ -21,32 +20,26 @@ group: manual
</tr>
</table>
-
-## 2. Enabling Cassandra Interpreter
-
- In a notebook, to enable the **Cassandra** interpreter, click on the **Gear** icon and select **Cassandra**.
+## Enabling Cassandra Interpreter
+In a notebook, to enable the **Cassandra** interpreter, click on the **Gear** icon and select **Cassandra**.
<center>
<img src="../assets/themes/zeppelin/img/docs-img/cassandra-InterpreterBinding.png" width="25%" height="25%">
<br>
<img src="../assets/themes/zeppelin/img/docs-img/cassandra-InterpreterSelection.png" width="25%" height="25%">
- </center>
-
-
-## 3. Using the Cassandra Interpreter
+</center>
- In a paragraph, use **_%cassandra_** to select the **Cassandra** interpreter and then input all commands.
+## 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;`
+To access the interactive help, type `HELP;`
<center>
- <img src="../assets/themes/zeppelin/img/docs-img/cassandra-InteractiveHelp.png" width="50%" height="50%">
- </center>
-
-
-## 4. Interpreter Commands
+ <img src="../assets/themes/zeppelin/img/docs-img/cassandra-InteractiveHelp.png" width="50%" height="50%">
+</center>
- The **Cassandra** interpreter accepts the following commands.
+## Interpreter Commands
+The **Cassandra** interpreter accepts the following commands.
<center>
<table class="table-configuration">
@@ -83,14 +76,13 @@ group: manual
</table>
</center>
-## 5. CQL statements
-
+## 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';
+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:
@@ -104,293 +96,276 @@ Each statement should be separated by a semi-colon ( **;** ) except the special
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:
+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;
+USE spark_demo;
- SELECT * FROM albums_by_country LIMIT 1; SELECT * FROM countries LIMIT 1;
+SELECT * FROM albums_by_country LIMIT 1; SELECT * FROM countries LIMIT 1;
- SELECT *
- FROM artists
- WHERE login='jlennon';
+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;
+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
- );
+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).
+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');
+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>
+<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>
-## 6. Comments in statements
-
+## 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');
+#First comment
+INSERT INTO users(login,name) VALUES('jdoe','John DOE');
- /**
- Multi line
- comments
- **/
- Insert into users(login,name) vAlues('hsue','Helen SUE');
+/**
+ Multi line
+ comments
+ **/
+Insert into users(login,name) vAlues('hsue','Helen SUE');
```
-
-## 7. Syntax Validation
-
-The interpreters is shipped with a built-in syntax validator. This validator only checks for basic syntax errors.
+## 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**.
-
-## 8. Schema commands
-
+## 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.
+
+<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>
+
+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.
<center>
</center>
+## Runtime Parameters
-## 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.
+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:
-<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>
+<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>
- Some parameters only accept restricted values:
+Some parameters only accept restricted values:
-<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>
+<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>
>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;
- CREATE TABLE IF NOT EXISTS spark_demo.ts(
- key int PRIMARY KEY,
- value text
- );
- TRUNCATE spark_demo.ts;
-
- # Timestamp in the past
- @timestamp=10
+# 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;
+# 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;
+# 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');
+# 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;
+# 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.
-
-## 10. Support for Prepared Statements
-
-For performance reason, it is better to prepare statements before-hand and reuse them later by providing bound values.
+## 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**
@@ -400,47 +375,41 @@ This interpreter provides 3 commands to handle prepared and bound statements:
Example:
```
+@prepare[statement_name]=...
- @prepare[statement_name]=...
-
- @bind[statement_name]=’text’, 1223, ’2015-07-30 12:00:01’, null, true, [‘list_item1’, ’list_item2’]
+@bind[statement_name]=’text’, 1223, ’2015-07-30 12:00:01’, null, true, [‘list_item1’, ’list_item2’]
- @bind[statement_name_with_no_bound_value]
+@bind[statement_name_with_no_bound_value]
- @remove_prepare[statement_name]
+@remove_prepare[statement_name]
```
-#### a. @prepare
-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.
-
+#### @prepare
+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.albums LIMIT ?
-
- @prepare[select]=SELECT * FROM spark_demo.artists 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.
+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)**.
-
-#### b. @bind
+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)**.
+#### @bind
Once the statement is prepared ( possibly in a separated notebook/paragraph ). You can bind values to it:
```
- @bind[select_first]=10
+@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:
@@ -460,30 +429,23 @@ Bound values are not mandatory for the `@bind` statement. However if you provide
> 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;
+> ```sql
+> BEGIN BATCH
+> @bind[insert_user]='jdoe','John DOE'
+> UPDATE users SET age = 27 WHERE login='hsue';
+> APPLY BATCH;
> ```
-#### c. @remove_prepare
-
-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.
+#### @remove_prepare
+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.
+## 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.
-## 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 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.
+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:
@@ -494,13 +456,12 @@ Example:
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.
+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_**.
+> 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**:
@@ -510,264 +471,254 @@ It is also possible to use dynamic forms for **prepared statements**:
{% endraw %}
-
-## 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`.
+## 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.
+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.
+
<center>
</center>
-In the interpreter creation form, put **cass-instance2** as **Name** and select the **cassandra**
-in the interpreter drop-down list
+In the interpreter creation form, put **cass-instance2** as **Name** and select the **cassandra** in the interpreter drop-down list
+
<center>
</center>
- Click on **Save** to create the new interpreter instance. Now you should be able to see it in the interpreter list.
-
+Click on **Save** to create the new interpreter instance. Now you should be able to see it in the interpreter list.
+
<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.
+You should be able to see and select the **cass-instance2** interpreter instance in the available interpreter list instead of the standard **cassandra** instance.
<center>
</center>
-
-## 13. Interpreter Configuration
-
+## 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
+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>
- <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>
-
-
-## 14. Bugs & Contacts
+## 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
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d157aeb/docs/interpreter/elasticsearch.md
----------------------------------------------------------------------
diff --git a/docs/interpreter/elasticsearch.md b/docs/interpreter/elasticsearch.md
index ba1b6f7..7b70528 100644
--- a/docs/interpreter/elasticsearch.md
+++ b/docs/interpreter/elasticsearch.md
@@ -6,13 +6,10 @@ group: manual
---
{% include JB/setup %}
-
## Elasticsearch Interpreter for Apache Zeppelin
[Elasticsearch](https://www.elastic.co/products/elasticsearch) is a highly scalable open-source full-text search and analytics engine. It allows you to store, search, and analyze big volumes of data quickly and in near real time. It is generally used as the underlying engine/technology that powers applications that have complex search features and requirements.
-<br />
-## 1. Configuration
-
+## Configuration
<table class="table-configuration">
<tr>
<th>Property</th>
@@ -45,24 +42,20 @@ group: manual
</center>
-
> **Note #1 :** You can add more properties to configure the Elasticsearch client.
> **Note #2 :** If you use Shield, you can add a property named `shield.user` with a value containing the name and the password ( format: `username:password` ). For more details about Shield configuration, consult the [Shield reference guide](https://www.elastic.co/guide/en/shield/current/_using_elasticsearch_java_clients_with_shield.html). Do not forget, to copy the shield client jar in the interpreter directory (`ZEPPELIN_HOME/interpreters/elasticsearch`).
-<br />
-## 2. Enabling the Elasticsearch Interpreter
-
+## Enabling the Elasticsearch Interpreter
In a notebook, to enable the **Elasticsearch** interpreter, click the **Gear** icon and select **Elasticsearch**.
-<br />
-## 3. Using the Elasticsearch Interpreter
-
+## Using the Elasticsearch Interpreter
In a paragraph, use `%elasticsearch` to select the Elasticsearch interpreter and then input all commands. To get the list of available commands, use `help`.
```bash
-| %elasticsearch
-| help
+%elasticsearch
+help
+
Elasticsearch interpreter:
General format: <command> /<indices>/<types>/<id> <option> <JSON>
- indices: list of indices separated by commas (depends on the command)
@@ -84,19 +77,17 @@ Commands:
> **Tip :** Use ( Ctrl + . ) for autocompletion.
-
### Get
With the `get` command, you can find a document by id. The result is a JSON document.
```bash
-| %elasticsearch
-| get /index/type/id
+%elasticsearch
+get /index/type/id
```
Example:
-
### Search
With the `search` command, you can send a search query to Elasticsearch. There are two formats of query:
@@ -106,53 +97,50 @@ With the `search` command, you can send a search query to Elasticsearch. There a
* This is a shortcut to a query like that: `{ "query": { "query_string": { "query": "__HERE YOUR QUERY__", "analyze_wildcard": true } } }`
* See [Elasticsearch query string syntax](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html#query-string-syntax) for more details about the content of such a query.
-
```bash
-| %elasticsearch
-| search /index1,index2,.../type1,type2,... <JSON document containing the query or query_string elements>
+%elasticsearch
+search /index1,index2,.../type1,type2,... <JSON document containing the query or query_string elements>
```
If you want to modify the size of the result set, you can add a line that is setting the size, before your search command.
```bash
-| %elasticsearch
-| size 50
-| search /index1,index2,.../type1,type2,... <JSON document containing the query or query_string elements>
+%elasticsearch
+size 50
+search /index1,index2,.../type1,type2,... <JSON document containing the query or query_string elements>
```
-
> A search query can also contain [aggregations](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations.html). If there is at least one aggregation, the result of the first aggregation is shown, otherwise, you get the search hits.
-
Examples:
* With a JSON query:
```bash
-| %elasticsearch
-| search / { "query": { "match_all": { } } }
-|
-| %elasticsearch
-| search /logs { "query": { "query_string": { "query": "request.method:GET AND status:200" } } }
-|
-| %elasticsearch
-| search /logs { "aggs": {
-| "content_length_stats": {
-| "extended_stats": {
-| "field": "content_length"
-| }
-| }
-| } }
+ %elasticsearch
+ search / { "query": { "match_all": { } } }
+
+ %elasticsearch
+ search /logs { "query": { "query_string": { "query": "request.method:GET AND status:200" } } }
+
+ %elasticsearch
+ search /logs { "aggs": {
+ "content_length_stats": {
+ "extended_stats": {
+ "field": "content_length"
+ }
+ }
+ } }
```
* With query_string elements:
```bash
-| %elasticsearch
-| search /logs request.method:GET AND status:200
-|
-| %elasticsearch
-| search /logs (404 AND (POST OR DELETE))
+ %elasticsearch
+ search /logs request.method:GET AND status:200
+
+ %elasticsearch
+ search /logs (404 AND (POST OR DELETE))
```
> **Important** : a document in Elasticsearch is a JSON document, so it is hierarchical, not flat as a row in a SQL table.
@@ -199,13 +187,12 @@ Examples:
* With a query containing a multi-bucket aggregation:
-
### Count
With the `count` command, you can count documents available in some indices and types. You can also provide a query.
```bash
-| %elasticsearch
-| count /index1,index2,.../type1,type2,... <JSON document containing the query OR a query string>
+%elasticsearch
+count /index1,index2,.../type1,type2,... <JSON document containing the query OR a query string>
```
Examples:
@@ -216,34 +203,30 @@ Examples:
* With a query:
-
### Index
With the `index` command, you can insert/update a document in Elasticsearch.
```bash
-| %elasticsearch
-| index /index/type/id <JSON document>
-|
-| %elasticsearch
-| index /index/type <JSON document>
+%elasticsearch
+index /index/type/id <JSON document>
+
+%elasticsearch
+index /index/type <JSON document>
```
### Delete
With the `delete` command, you can delete a document.
```bash
-| %elasticsearch
-| delete /index/type/id
+%elasticsearch
+delete /index/type/id
```
-
### Apply Zeppelin Dynamic Forms
-
You can leverage [Zeppelin Dynamic Form]({{BASE_PATH}}/manual/dynamicform.html) inside your queries. You can use both the `text input` and `select form` parameterization features.
```bash
-| %elasticsearch
-| size ${limit=10}
-| search /index/type { "query": { "match_all": { } } }
+%elasticsearch
+size ${limit=10}
+search /index/type { "query": { "match_all": { } } }
```
-
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d157aeb/docs/interpreter/flink.md
----------------------------------------------------------------------
diff --git a/docs/interpreter/flink.md b/docs/interpreter/flink.md
index 6af339b..e1744c0 100644
--- a/docs/interpreter/flink.md
+++ b/docs/interpreter/flink.md
@@ -6,11 +6,9 @@ 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. Flink’s core is a streaming dataflow engine that provides data distribution, communication, and fault tolerance for distributed computations over data streams. Flink also builds batch processing on top of the streaming engine, overlaying native iteration support, managed memory, and program optimization.
-<br>
## 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.
@@ -38,10 +36,8 @@ At the "Interpreters" menu, you have to create a new Flink interpreter and provi
For more information about Flink configuration, you can find it [here](https://ci.apache.org/projects/flink/flink-docs-release-0.10/setup/config.html).
## 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 [Interactive data analysis with Apache Flink](http://www.slideshare.net/tillrohrmann/data-analysis-49806564) for Apache Flink Meetup.
-
```
%sh
rm 10.txt.utf-8
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d157aeb/docs/interpreter/geode.md
----------------------------------------------------------------------
diff --git a/docs/interpreter/geode.md b/docs/interpreter/geode.md
index 250495a..53a912e 100644
--- a/docs/interpreter/geode.md
+++ b/docs/interpreter/geode.md
@@ -6,10 +6,7 @@ group: manual
---
{% include JB/setup %}
-
## Geode/Gemfire OQL Interpreter for Apache Zeppelin
-
-<br/>
<table class="table-configuration">
<tr>
<th>Name</th>
@@ -23,7 +20,6 @@ group: manual
</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)
@@ -38,7 +34,6 @@ This interpreter supports the [Geode](http://geode.incubator.apache.org/) [Objec
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 _cannot_ connect to different Geode clusters in the same `Notebook`. This is a known Zeppelin limitation.
@@ -53,38 +48,35 @@ In the `Notebook` click on the `settings` icon in the top right corner. The sele
### Configuration
You can modify the configuration of the Geode from the `Interpreter` section. The Geode interpreter expresses 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>
+<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: Always 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 specification does not support [Geode Regions](https://cwiki.apache.org/confluence/display/GEODE/Index#Index-MainConceptsandComponents) mutation operations. To `create`/`destroy` regions one should use the [GFSH](http://geode-docs.cfapps.io/docs/tools_modules/gfsh/chapter_overview.html) shell tool instead. In the following it is assumed that the GFSH is colocated with Zeppelin server.
```bash
@@ -105,9 +97,7 @@ EOF
Above snippet re-creates two regions: `regionEmployee` and `regionCompany`. Note that you have to explicitly 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
-
-
+#### Basic OQL
```sql
%geode.oql
SELECT count(*) FROM /regionEmployee
@@ -144,12 +134,9 @@ Following query will return the EntrySet value as a Blob:
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
@@ -159,7 +146,6 @@ gfsh -e "connect" -e "list members"
```
#### Apply Zeppelin Dynamic Forms
-
You can leverage [Zeppelin Dynamic Form](../manual/dynamicform.html) inside your OQL queries. You can use both the `text input` and `select form` parameterization features
```sql
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d157aeb/docs/interpreter/hive.md
----------------------------------------------------------------------
diff --git a/docs/interpreter/hive.md b/docs/interpreter/hive.md
index c9e0a6c..5871feb 100644
--- a/docs/interpreter/hive.md
+++ b/docs/interpreter/hive.md
@@ -6,12 +6,10 @@ group: manual
---
{% include JB/setup %}
-
## Hive Interpreter for Apache Zeppelin
The [Apache Hive](https://hive.apache.org/) ™ data warehouse software facilitates querying and managing large datasets residing in distributed storage. Hive provides a mechanism to project structure onto this data and query the data using a SQL-like language called HiveQL. At the same time this language also allows traditional map/reduce programmers to plug in their custom mappers and reducers when it is inconvenient or inefficient to express this logic in HiveQL.
-
-## 1. Configuration
+### Configuration
<table class="table-configuration">
<tr>
<th>Property</th>
@@ -71,9 +69,8 @@ The [Apache Hive](https://hive.apache.org/) ™ data warehouse software facilita
</table>
This interpreter provides multiple configuration with `${prefix}`. User can set a multiple connection properties by this prefix. It can be used like `%hive(${prefix})`.
-
-## 2. How to use
+## How to use
Basically, you can use
```sql
@@ -92,7 +89,6 @@ select * from my_table;
You can also run multiple queries up to 10 by default. Changing these settings is not implemented yet.
### Apply Zeppelin Dynamic Forms
-
You can leverage [Zeppelin Dynamic Form]({{BASE_PATH}}/manual/dynamicform.html) inside your queries. You can use both the `text input` and `select form` parameterization features.
```sql
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d157aeb/docs/interpreter/ignite.md
----------------------------------------------------------------------
diff --git a/docs/interpreter/ignite.md b/docs/interpreter/ignite.md
index 963c7d9..6fa1f61 100644
--- a/docs/interpreter/ignite.md
+++ b/docs/interpreter/ignite.md
@@ -18,55 +18,54 @@ You can use Zeppelin to retrieve distributed data from cache using Ignite SQL in
### 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
+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">
+<table class="table-configuration">
+ <tr>
+ <th>Property Name</th>
+ <th>value</th>
+ <th>Description</th>
+ </tr>
<tr>
- <th>Property Name</th>
- <th>value</th>
- <th>Description</th>
+ <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.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>
+ <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.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>
+ <td>ignite.config.url</td>
+ <td></td>
+ <td>Configuration URL. Overrides all other settings.</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>
+ <td>ignite.jdbc.url</td>
+ <td>jdbc:ignite:cfg://default-ignite-jdbc.xml</td>
+ <td>Ignite JDBC connection URL.</td>
</tr>
- </table>
+ <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>
@@ -82,35 +81,33 @@ 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
- ```
-
- 
-
+```
+%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._
+```
+%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._
- import scala.collection.JavaConversions._
+val cache: IgniteCache[AffinityUuid, String] = ignite.cache("words")
- 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 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()
- val res = cache.query(qry).getAll()
+collectionAsScalaIterable(res).foreach(println _)
+```
- 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/0d157aeb/docs/interpreter/lens.md
----------------------------------------------------------------------
diff --git a/docs/interpreter/lens.md b/docs/interpreter/lens.md
index 5fc7a45..c883f10 100644
--- a/docs/interpreter/lens.md
+++ b/docs/interpreter/lens.md
@@ -16,69 +16,70 @@ group: manual
### 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)
- ```
+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 edit Lens interpreter or create new one. Zeppelin provides these properties for Lens.
- <table class="table-configuration">
+<table class="table-configuration">
<tr>
- <th>Property Name</th>
- <th>value</th>
- <th>Description</th>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <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>
+ <td>xxx</td>
+ <td>yyy</td>
+ <td>anything else from [Configuring lens server](https://lens.apache.org/admin/config-server.html)</td>
</tr>
- </table>
+</table>
### Interpreter Bindging for Zeppelin Notebook
-After configuring Lens interpreter, create your own notebook, then you can bind interpreters like below image.
+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).
@@ -90,84 +91,79 @@ As you can see in this video, they are using Lens Client Shell(./bin/lens-cli.sh
<li> Create and Use(Switch) Databases.
- ```
- create database newDb
- ```
-
- ```
- use newDb
- ```
-
+```
+create database newDb
+```
+
+```
+use newDb
+```
+
<li> Create Storage.
- ```
- create storage your/path/to/lens/client/examples/resources/db-storage.xml
- ```
-
+```
+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
- ```
-
+```
+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
- ```
+```
+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
- ```
+```
+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
- ```
+
+```
+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')
- ```
-
-
- 
+
+```
+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/0d157aeb/docs/interpreter/postgresql.md
----------------------------------------------------------------------
diff --git a/docs/interpreter/postgresql.md b/docs/interpreter/postgresql.md
index 9d3a283..54def09 100644
--- a/docs/interpreter/postgresql.md
+++ b/docs/interpreter/postgresql.md
@@ -6,10 +6,7 @@ group: manual
---
{% include JB/setup %}
-
## PostgreSQL, HAWQ Interpreter for Apache Zeppelin
-
-<br/>
<table class="table-configuration">
<tr>
<th>Name</th>
@@ -23,7 +20,6 @@ group: manual
</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:
@@ -32,11 +28,9 @@ This interpreter seamlessly supports the following SQL data processing engines:
* [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 _cannot_ connect to different databases in the same `Notebook`. This is a known Zeppelin limitation.
@@ -51,47 +45,45 @@ In the `Notebook` click on the `settings` icon in the top right corner. The sele
### 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>
-
+<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
+#### 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:
@@ -121,7 +113,6 @@ 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
@@ -131,6 +122,7 @@ psql -h phd3.localdomain -U gpadmin -p 5432 <<EOF
\q
EOF
```
+
This will produce output like this:
```
@@ -146,7 +138,6 @@ This will produce output like this:
```
#### Apply Zeppelin Dynamic Forms
-
You can leverage [Zeppelin Dynamic Form](../manual/dynamicform.html) inside your queries. You can use both the `text input` and `select form` parametrization features
```sql
@@ -157,8 +148,8 @@ 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
+#### Example HAWQ PXF/HDFS Tables
Create HAWQ external table that read data from tab-separated-value data in HDFS.
```sql
@@ -168,11 +159,13 @@ CREATE EXTERNAL TABLE retail_demo.payment_methods_pxf (
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
select * from retail_demo.payment_methods_pxf
```
+
### Auto-completion
The PSQL Interpreter provides a basic auto-completion functionality. On `(Ctrl+.)` it list the most relevant suggestions in a pop-up window. In addition to the SQL keyword the interpreter provides suggestions for the Schema, Table, Column names as well.
http://git-wip-us.apache.org/repos/asf/incubator-zeppelin/blob/0d157aeb/docs/interpreter/scalding.md
----------------------------------------------------------------------
diff --git a/docs/interpreter/scalding.md b/docs/interpreter/scalding.md
index 40ec8b1..f84636a 100644
--- a/docs/interpreter/scalding.md
+++ b/docs/interpreter/scalding.md
@@ -6,7 +6,6 @@ group: manual
---
{% include JB/setup %}
-
## Scalding Interpreter for Apache Zeppelin
[Scalding](https://github.com/twitter/scalding) is an open source Scala library for writing MapReduce jobs.
@@ -18,20 +17,20 @@ mvn clean package -Pscalding -DskipTests
```
### Enabling the Scalding Interpreter
-
In a notebook, to enable the **Scalding** interpreter, click on the **Gear** icon,select **Scalding**, and hit **Save**.
-
- <center>
- 
- 
- </center>
+<center>
+
+
+
+
+
+</center>
### Configuring the Interpreter
Zeppelin comes with a pre-configured Scalding interpreter in local mode, so you do not need to install anything.
### Testing the Interpreter
-
In example, by using the [Alice in Wonderland](https://gist.github.com/johnynek/a47699caa62f4f38a3e2) tutorial, we will count words (of course!), and plot a graph of the top 10 words in the book.
```
@@ -75,4 +74,4 @@ If you click on the icon for the pie chart, you should be able to see a chart li
### Current Status & Future Work
The current implementation of the Scalding interpreter does not support canceling jobs, or fine-grained progress updates.
-The pre-configured Scalding interpreter only supports Scalding in local mode. Hadoop mode for Scalding is currently unsupported, and will be future work (contributions welcome!).
\ No newline at end of file
+The pre-configured Scalding interpreter only supports Scalding in local mode. Hadoop mode for Scalding is currently unsupported, and will be future work (contributions welcome!).