ConfD configuration API incorrectly accepted parameters as "null"
Details
| Detail name | Value |
|---|---|
| Changelog Number | 21225 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | Exasol 8.0.0 |
| Fix Versions | Exasol 8.29.2 |
| Resolution Date | 2024-08-29 |
Description
The ConfD Exasol configuration API incorrectly accepted optional parameters that were set to null / None, even if they were documented as a different type, such as a string or integer.
Workaround
Effect of unexpected null / None values might have been different depending on a ConfD job, so there is no specific workaround.
Fix
This now correctly raises an error, preventing accidental misuse.
