You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/install/install.md
+36Lines changed: 36 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -235,3 +235,39 @@ After successful start, visit [http://localhost:8080](http://localhost:8080) wit
235
235
```
236
236
bin/zeppelin-daemon.sh stop
237
237
```
238
+
239
+
#### Start Zeppelin with a service manager such as upstart
240
+
241
+
Zeppelin can auto start as a service with an init script, such as services managed by upstart.
242
+
243
+
The following is an example upstart script to be saved as `/etc/init/zeppelin.conf`
244
+
This example has been tested with Ubuntu Linux.
245
+
This also allows the service to be managed with commands such as
246
+
247
+
`sudo service zeppelin start`
248
+
`sudo service zeppelin stop`
249
+
`sudo service zeppelin restart`
250
+
251
+
Other service managers could use a similar approach with the `upstart` argument passed to the zeppelin-daemon.sh script: `bin/zeppelin-daemon.sh upstart`
252
+
253
+
##### zeppelin.conf
254
+
255
+
```
256
+
description "zeppelin"
257
+
258
+
start on (local-filesystems and net-device-up IFACE!=lo)
259
+
stop on shutdown
260
+
261
+
# Respawn the process on unexpected termination
262
+
respawn
263
+
264
+
# respawn the job up to 7 times within a 5 second period.
265
+
# If the job exceeds these values, it will be stopped and marked as failed.
266
+
respawn limit 7 5
267
+
268
+
# zeppelin was installed in /usr/share/zeppelin in this example
Copy file name to clipboardExpand all lines: docs/interpreter/jdbc.md
+18-16Lines changed: 18 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,14 +56,15 @@ It is not necessary to add driver jar to the classpath for PostgreSQL as it is i
56
56
57
57
#### Simple connection
58
58
59
-
Before creating the interpreter it is necessary to add to the Zeppelin classpath the path of the JDBC you want to use, to do it you must edit the file `zeppelin-daemon.sh` as shown:
59
+
Prior to creating the interpreter it is necessary to add maven coordinate or path of the JDBC driver to the Zeppelin classpath. To do this you must edit dependencies artifact(ex. `mysql:mysql-connector-java:5.1.38`) in interpreter menu as shown:
For create the interpreter you need to specify connection parameters as shown in the table.
67
+
To create the interpreter you need to specify connection parameters as shown in the table.
67
68
68
69
<tableclass="table-configuration">
69
70
<tr>
@@ -94,14 +95,15 @@ For create the interpreter you need to specify connection parameters as shown in
94
95
95
96
#### Multiple connections
96
97
97
-
This JDBC interpreter also allows connections to multiple data sources. For every connection is necessary a prefix for reference in the paragraph this way `%jdbc(prefix)`. Before creating the interpreter it is necessary to add to the Zeppelin classpath all paths to access to each driver's jar file you want to use, to do it you must edit the file `zeppelin-daemon.sh` as following:
98
+
JDBC interpreter also allows connections to multiple data sources. It is necessary to set a prefix for each connection to reference it in the paragraph in the form of `%jdbc(prefix)`. Before you create the interpreter it is necessary to add each driver's maven coordinates or JDBC driver's jar file path to the Zeppelin classpath. To do this you must edit the dependencies of JDBC interpreter in interpreter menu as following:
You can add all the jars you need to make multiple connections into the same interpreter. To create the interpreter you must specify the parameters, for example we will create two connections to PostgreSQL and Redshift, the respective prefixes are `default` and `redshift`:
You can add all the jars you need to make multiple connections into the same JDBC interpreter. To create the interpreter you must specify the parameters. For example we will create two connections to MySQL and Redshift, the respective prefixes are `default` and `redshift`:
105
107
106
108
<tableclass="table-configuration">
107
109
<tr>
@@ -114,19 +116,19 @@ You can add all the jars you need to make multiple connections into the same int
0 commit comments