BuiltinScriptLanguageName has been moved to "Global" section of EXAConf
Details
| Detail name | Value |
|---|---|
| Changelog Number | 21755 |
| Type | Improvement |
| Status | Resolved |
| Fix Versions | Exasol 8.32.0 |
| Resolution Date | 2024-11-08 |
Background
Previously, the path to the standard Script Language Container was a per-database setting, configurable via db_create and db_configure ConfD jobs.
BuiltinScriptLanguageName was a per-database setting in EXAConf.
Improvement
Since there is no known use case for setting different values for this field for different databases, it has been moved to the Global section of respective configuration file EXAConf instead. The builtin_script_language_name option has been removed from the db_create and db_configure ConfD jobs. Therefore you need to edit EXAConf, manually to change this field, however a separate fix will soon set the value automatically to match c4 info $DB_ALIAS Dependencies.SLC, so there should be no more need to adjust this manually.
The behavior is otherwise unchanged. There is no need to delete the old BuiltinScriptLanguageName entries in an existing EXAConf’s database section(s); they will be removed automatically during the update. Manually adding a BuiltinScriptLanguageName entry to a database section in EXAConf will be silently ignored from now on.
Editing of EXAConf file should be done only when requested by Exasol Support.
Changed behavior
The builtin_script_language_name option has been removed from the db_create and db_configure ConfD jobs.
