Overview
The Script-Languages-Container-Tool (exaslct) is the build tool for the script language container. You can build, export and upload script-language container from so-called flavors which are description how to build the script language container. You can find pre-defined flavors in the script-languages-release repository. There we also described how you could customize these flavors to your needs.
In a Nutshell
Prerequisites
Note: Since version 1.0.0 the “starter scripts” shipped with previous version, which pulled the exaslct docker container runtime, were removed. If you can’t use Python3, you still can use our AI-lab which provides VM images, AMI images and a Docker images, all capable of building script-language-container.
For running
In order to use this tool, your system needs to fulfill the following prerequisites:
Software
Linux
Python3 >= 3.10
Docker >= 17.05
with support for multi-stage builds required
host volume mounts need to be allowed
System Setup
We recommend at least 50 GB free disk space on the partition where Docker stores its images, on linux Docker typically stores the images at /var/lib/docker.
For the partition where the output directory (default: ./.build_output) is located we recommend additionally at least 10 GB free disk space.
Further, prerequisites might be necessary for specific tasks. These are listed under the corresponding section.
Installation
In general, it’s good practice to install the package in a virtual environment, using venv or Poetry.
Pip via PyPi
python3 -m pip install exasol-script-languages-container-toolPipx via Pypi
If you plan to use exasol-script-languages-container-tool on the command line only via the exaslct script, we suggest the installation via pipx:
pipx install exasol-script-languages-container-toolUsage
For simplicity the following examples use the script version (exaslct), which will be installed together with the Python package. The script is just an alias for python3 -m exasol.slc.tool.main.
How to build an existing flavor?
Create the language container and export it to the local file system
exaslct export --flavor-path=flavors/<flavor-name> --export-path <export-path>or deploy it directly to the BucketFS (both http and https are supported)
exaslct deploy --flavor-path=flavors/<flavor-name> --bucketfs-host <hostname-or-ip> --bucketfs-port <port> \
--bucketfs-user w --bucketfs-password <password> --bucketfs-name <bucketfs-name> \
--bucket <bucket-name> --path-in-bucket <path/in/bucket> --bucketfs-use-https 1Once it is successfully deployed, it will print the ALTER SESSION statement that can be used to activate the script language container in the database.
How to activate a script language container in the database
If you uploaded a container manually, you can generate the language activation statement with
exaslct generate-language-activation --flavor-path=flavors/<flavor-name> --bucketfs-name <bucketfs-name> \
--bucket-name <bucket-name> --path-in-bucket <path/in/bucket> --container-name <container-name>where <container-name> is the name of the uploaded archive without its file extension. To activate the language, execute the generated statement in your database session to activate the container for the current session or system wide.
This command will print a SQL statement to activate the language similar to the following one:
ALTER SESSION SET SCRIPT_LANGUAGES='<LANGUAGE_ALIAS>=localzmq+protobuf:///<bucketfs-name>/<bucket-name>/<path-in-bucket>/<container-name>?lang=<language>#buckets/<bucketfs-name>/<bucket-name>/<path-in-bucket>/<container-name>/exaudf/exaudfclient[_py3]';Please, refer to the User Guide. for more detailed information, how to use exalsct.
Features
Build a script language container as docker images
Export a script language container as an archive which can be used for extending Exasol UDFs
Upload a script language container as an archive to the Exasol DB’s BucketFS
Generating the activation command for a script language container
Can use Docker registries, such as Docker Hub, as a cache to avoid rebuilding image without changes
Can push Docker images to Docker registries
Run tests for you container against an Exasol DB (docker-db or external db)
📚 Documentation
For further details, check out latest documentation.
1 maintainer
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file exasol_script_languages_container_tool-4.2.0.tar.gz.
File metadata
- Download URL: exasol_script_languages_container_tool-4.2.0.tar.gz
- Upload date:
- Size: 57.9 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via:
poetry/2.3.0 CPython/3.10.20 Linux/6.17.0-1020-azure
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
95034a7aad3ae90a87e5d479d2ce9c3f4b3944c5d4944dd034abcf57f15b04c2
|
|
| MD5 |
a2e70c72e37e657a93dd665172f42689
|
|
| BLAKE2b-256 |
ce70b1fcd43c2e3117237528e214ee3beadc1dbcc22d3e7448c56e0ca9638fd7
|
File details
Details for the file exasol_script_languages_container_tool-4.2.0-py3-none-any.whl.
File metadata
- Download URL: exasol_script_languages_container_tool-4.2.0-py3-none-any.whl
- Upload date:
- Size: 116.7 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via:
poetry/2.3.0 CPython/3.10.20 Linux/6.17.0-1020-azure
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
7f3f0ae14e089f9faa90d96d3cf655cc8a4ab3ce32ee4b93842b2618421f2d0c
|
|
| MD5 |
826f2a9404b89ce17e7bea7eb44fbf88
|
|
| BLAKE2b-256 |
f2f7a9cdc5c3651f3c231b13d391219a82b87c0e81be7b5bc783207311a3be24
|
