Releases: exasol/script-languages
UDFClient Build Improvements
We recommend updating to this release, because it restores a few percent of performance compared to the releases since Release 20190601
- Change compiler flags configuration for Build to achieve similar compiler optimization for the UDFClient than with the old build bash script
- Activate link time optimization for the Build which allows the compiler more optimizations
- Remove unnecessary shared libraries for java, because these increased the loading time of the UDFClient
- Simplify the rpath workaround by moving it to the java_repository.bzl
- Build can now produce two variants of the executable, one with hard coded paths and one with a wrapper script which sets the paths via environment variables. The executable with hard coded paths only runs in the container environment, but has few percent faster startup than the wrapper script. The wrapper script can be used for local debugging and testing outside of the container environment.
Add row level security support to standard flavor
This release adds dependencies you need for implementing row level security in Exasol to the standard flavor. You can find an example, how to implement row level security with the standard flavor in the tests.
Additional minor changes:
Add build information to docker images and final container and fix image deployment
Exaslct now adds build information to the docker images and the final container to easier trace down which image introduces a problem. For that, we include the following information into the images and the container:
- Configuration which was used to create the images and the container
- Dockerfiles of the images
- The package lists that each image installs
NOTE: Currently, Travis CI is not able to upload the pre-packaged python3-ds-cuda-preview container to Github, because it fails with the following Error: travis-ci/travis-ci#8553
Furthermore, Github Releases doesn't allow the upload of files larger than 2 GB either. So, for the time being, we provide the pre-packaged python3-ds-cuda-preview container under the following link:
https://storage.googleapis.com/exasol-integration-demo/python3-ds-cuda-preview-EXASOL-6.1.0-release-MIIRTB2R4E6YQ5W2H3GDOUDTQT5KDJZA535KOORSAR3WV7YF2VWQ.tar.gz
Additional minor changes:
- Set lower bounds for the version of the python packages in the Pipfile for exaslct
- Fix image deployment: now all images get deployed instead only the top-level images
New flavor python3-ds-cuda-preview
This release adds a new flavor which enables the usage of CUDA CPUs in the Container. This is currently specifically meant for Tensorflow, but will be extended to other libraries.
The flavor installs the CUDA Driver Version 410.104 without the Kernel module and the CUDA SDK Version 10 into the Container. These versions are specifically chosen for Tensorflow for GPUs in Version 1.13.1, because Tensorflow installed with pip depends on specific version of libcuda.so. To use Tensorflow with GPUs the Host system needs the complete CUDA Driver with the same version installed.
NOTE: Currently, Travis CI is not able to upload the pre-packaged python3-ds-cuda-preview container to Github, because it fails with the following Error: travis-ci/travis-ci#8553
Furthermore, Github Releases doesn't allow the upload of files larger than 2 GB either. So, for the time being, we provide the pre-packaged python3-ds-cuda-preview container under the following link:
https://storage.googleapis.com/exasol-integration-demo/python3-ds-cuda-preview-EXASOL-6.1.0-release-OHJFKDQVKZYGSP7AWQWAYWBECT577SK6DG5JBR47Z2TL7GQ2M4OA.tar.gz
Further, minor changes:
- bugfixes for the exaslct starter script on some installations of python3
- bugfix of the travis.yaml which now pushes all images to the build caches during deployment
- added PyYAML to all python3-ds-* flavors
20190601
This is a binary release of several Script Language Container Flavors from following Travis CI Job:
https://travis-ci.org/exasol/script-languages/jobs/540135301
It is the first release which was build by the new build system Exaslct and uses the new definition of the Flavors.
The CI Job has uploaded the base docker images, from which the containers were build from, to Docker Hub:
https://hub.docker.com/r/exasol/script-language-container
Exaslct will download these base images when you build containers. Normally, this is faster than building the images from scratch.
The release tag is the date of the release.