Java 17 as default and new Script Options Parser

Details

Detail name Value
Changelog Number 24714
Type Improvement
Status Resolved
Fix Versions Exasol 2025.1.0
Resolution Date 2025-07-08

Background

Exasol database allows users to create and run scripts (User Defined Functions) in several languages.

Database component implementing support for those languages is called Script Language Container (SLC).

There are containers built into database installations and also custom ones that could be prepared by users on-demand and uploaded to BucketFS for further use. See Adding New Packages to Existing Script Languages for more details.

Improvement

New Packages

The built-in Script Language Container is updated from version script-languages-release version 9.2.0 to script-languages-release version 9.5.2.

Detailed package changes can be found at:

Java 17

This release introduces the Java 17 Container as default Java language for Java UDFs.

It’s still possible to use Java 11 for existing Java UDF’s by setting:

ALTER SESSION SET SCRIPT_LANGUAGES='R=builtin_r PYTHON3=builtin_python3 JAVA=builtin_java11';

or

ALTER SYSTEM SET SCRIPT_LANGUAGES='R=builtin_r PYTHON3=builtin_python3 JAVA=builtin_java11';

New Script Options Parser

The Java 17 Script-Languages-Container uses the new Script-Options-Parser, see JVM options for details.

The old parser still can be used:

  • Implicitly by using the Java 11 Script-Languages-Container (See section “Java 17”)
  • By setting %env SCRIPT_OPTIONS_PARSER_VERSION=1; in the UDF

Changed behavior

1. Several packages were updated 1. Java 17 is the new default Java version for Java UDFs 2. New Script-Options-Parser for Java UDF's