4
4
5
5
An extension would typically use [ UDF scripts] ( https://docs.exasol.com/db/latest/database_concepts/udf_scripts.htm )
6
6
to enable certain custom functionality within a database. In most cases, UDF scripts must be backed by a
7
- [ Script Language Container (SLC)] ( https://github.com/exasol/script-languages-release/ ) , that must be installed in the
7
+ [ Script Language Container (SLC)] ( https://github.com/exasol/script-languages-release/ ) , that needs to be installed in the
8
8
Exasol Database. An SLC allows the installation of the chosen programming language and necessary dependencies in the
9
9
Exasol Database.
10
10
11
- The language container for a particular Extension gets downloaded and installed by executing a deployment script
12
- similar to the one below.
11
+ The deployment of the language container is typically included in the installation of the Extension. It should also
12
+ be possible to install the SLC separately using the same or a different CLI command. Please check the user guide of
13
+ a particular extension for details. Below is an example of an extension installation command.
13
14
14
15
``` buildoutcfg
15
- python -m <exasol_extension>.deploy language-container <options>
16
+ python -m <exasol_extension>.deploy <options>
16
17
```
17
18
18
- The name of the script (``` <exasol_extension>.deploy ``` in the above command) and the command name
19
- (e.g. ``` language-container ``` ) can vary from one extension to another. Please check the user guide of a particular
20
- extension. The rest of the command line will have a common format. It will include some of the options defined below.
21
- The choice of options is primarily determined by the storage backend being used - On-Prem or SaaS.
19
+ The name of the script (``` <exasol_extension>.deploy ``` in the above command) can vary from one extension to another.
20
+ The rest of the command line will have a common format. It will include some of the options defined below. The choice
21
+ of options is primarily determined by the storage backend being used - On-Prem or SaaS.
22
22
23
23
### List of options
24
24
@@ -32,36 +32,38 @@ an option in the command line, without providing its value. In this case, the co
32
32
interactively. For long values, such as the SaaS account id, it is more practical to copy/paste the value from
33
33
another source.
34
34
35
- | Option name | On-Prem | SaaS | Comment |
36
- | :-----------------------------| :-------:| :----:| :--------------------------------------------------------|
37
- | dsn | [ x] | | i.e. <db_host: db_port > |
38
- | db-user | [ x] | | |
39
- | db-pass | [ x] | | Env. [ DB_PASSWORD] |
40
- | bucketfs-name | [ x] | | |
41
- | bucketfs-host | [ x] | | |
42
- | bucketfs-port | [ x] | | |
43
- | bucketfs-user | [ x] | | |
44
- | bucketfs-password | [ x] | | Env. [ BUCKETFS_PASSWORD] |
45
- | bucketfs-use-https | [ x] | | Optional boolean, defaults to False |
46
- | bucket | [ x] | | |
47
- | saas-url | | [ x] | Env. [ SAAS_HOST] |
48
- | saas-account-id | | [ x] | Env. [ SAAS_ACCOUNT_ID] |
49
- | saas-database-id | | [ x] | Optional, Env. [ SAAS_DATABASE_ID] |
50
- | saas-database-name | | [ x] | Optional, provide if the database_id is unknown |
51
- | saas-token | | [ x] | Env. [ SAAS_TOKEN] |
52
- | path-in-bucket | [ x] | [ x] | |
53
- | language-alias | [ x] | [ x] | |
35
+ | Option name | On-Prem | SaaS | Comment |
36
+ | :-----------------------------| :-------:| :----:| :------------------------------------------------------------------- |
37
+ | dsn | [ x] | | i.e. <db_host: db_port > |
38
+ | db-user | [ x] | | |
39
+ | db-pass | [ x] | | Env. [ DB_PASSWORD] |
40
+ | bucketfs-name | [ x] | | |
41
+ | bucketfs-host | [ x] | | |
42
+ | bucketfs-port | [ x] | | |
43
+ | bucketfs-user | [ x] | | |
44
+ | bucketfs-password | [ x] | | Env. [ BUCKETFS_PASSWORD] |
45
+ | bucketfs-use-https | [ x] | | Optional boolean, defaults to False |
46
+ | bucket | [ x] | | |
47
+ | saas-url | | [ x] | Env. [ SAAS_HOST] |
48
+ | saas-account-id | | [ x] | Env. [ SAAS_ACCOUNT_ID] |
49
+ | saas-database-id | | [ x] | Optional, Env. [ SAAS_DATABASE_ID] |
50
+ | saas-database-name | | [ x] | Optional, provide if the database_id is unknown |
51
+ | saas-token | | [ x] | Env. [ SAAS_TOKEN] |
52
+ | path-in-bucket | [ x] | [ x] | |
53
+ | language-alias | [ x] | [ x] | |
54
54
| schema | [ x] | [ x] | Required if the user has no permission to create a database schema |
55
- | version | [ x] | [ x] | Optional, provide for downloading SLC from GitHub |
56
- | container-file | [ x] | [ x] | Optional, provide for uploading SLC file |
57
- | ssl-cert-path | [ x] | [ x] | Optional |
58
- | [ no-] use-ssl-cert-validation | [ x] | [ x] | Optional boolean, defaults to True |
59
- | ssl-client-cert-path | [ x] | | Optional |
60
- | ssl-client-private-key | [ x] | | Optional |
61
- | [ no-] upload-container | [ x] | [ x] | Optional boolean, defaults to True |
62
- | [ no-] alter-system | [ x] | [ x] | Optional boolean, defaults to True |
63
- | [ no-] allow-override | [ x] | [ x] | Optional boolean, defaults to False |
64
- | [ no-] wait_for_completion | [ x] | [ x] | Optional boolean, defaults to True |
55
+ | version | [ x] | [ x] | Optional, provide for downloading SLC from GitHub |
56
+ | container-file | [ x] | [ x] | Optional, provide for uploading SLC file |
57
+ | ssl-cert-path | [ x] | [ x] | Optional |
58
+ | [ no-] use-ssl-cert-validation | [ x] | [ x] | Optional boolean, defaults to True |
59
+ | ssl-client-cert-path | [ x] | | Optional |
60
+ | ssl-client-private-key | [ x] | | Optional |
61
+ | [ no-] upload-container | [ x] | [ x] | Optional boolean, defaults to True |
62
+ | [ no-] alter-system | [ x] | [ x] | Optional boolean, defaults to True |
63
+ | [ no-] allow-override | [ x] | [ x] | Optional boolean, defaults to False |
64
+ | [ no-] wait-for-completion | [ x] | [ x] | Optional boolean, defaults to True |
65
+ | deploy-timeout-minutes | [ x] | [ x] | Defaults to 10 minutes. |
66
+ | [ no-] display-progress | [ x] | [ x] | Optional boolean, defaults to True |
65
67
66
68
### Container selection
67
69
@@ -109,3 +111,13 @@ has already been uploaded one can use the `--no-upload-container` option to skip
109
111
By default, overriding language activation is not permitted. If a language with the same alias has already
110
112
been activated the command will result in an error. The activation can be overridden with the use of
111
113
the ` --allow-override ` option.
114
+
115
+ ## BucketFS connection object
116
+
117
+ Some extensions require the user to create a BucketFS connection object encapsulating the BucketFS credentials.
118
+ The creation of such an object in the database would also be a part of the extension installation. Like the
119
+ language container, the connection object can be created separately, using the same or a different command.
120
+ Please check the documentation of a particular extension for details.
121
+
122
+ Most of the options listed above in the Language Container Deployer sections are also relevant for the creation
123
+ of the connection object, should it be performed in a separate command.
0 commit comments