Version 8.0.0 Release Notes

Please view the list below for an overview of all changes in version 8.0.0. Version 8.0.0 was released on 2022-04-20.

Changed Behavior

Changelog Entry Changed Behavior
21276 Database now requires a certificate chain consisting of more than one certificate.
14096 The Exasol ADO.NET and ODBC driver will not set snapshot transactions by default to "OFF" at connect time.
14035 Auditing is now enabled by default.
14034 DB Default configuration for accepting clients are changed. From now on wards, the DB will accept only encrypted connections (Either TLS, or ChaCha) from the clients.
13966 Added JDBC and DRIVER as non-reserverd keywords
13863 ODBC: Truncation of string values follows ODBC standards (SQLGetData, SQLFetch or SQLFetchScroll)
13808 Sessions having read-only open transactions are no longer considered as active sessions.
13228 Applications which use UTF-8 strings in non-unicode ("W") functions must now setlocale() or use the connection string parameter "ConnectionLCCtype" so that the locale settings in the console match the data sent by the application.
12517 1. *The new join order optimizer is now default* 2. Due to the switch to the new standard join order optimizer the previous session configuration options for {{CONTROL SET JOIN OPTIMIZER}} were renamed to reflect that change. The old names are no longer usable: * {{DEFAULT}} is now {{LEGACY}} * {{EXPERIMENTAL}} is now {{STANDARD}} So the following statements will need adaptions in case you used them: {code:sql} CONTROL SET JOIN OPTIMIZER DEFAULT; CONTROL SET JOIN OPTIMIZER EXPERIMENTAL; {code} Also keep in mind that the changed default will invalidate the reason for some of those commands where they only set to the new standard. We recommend to try without those statements and rely on the improved new optimizer, instead. If you want to keep those statements the new syntax is: {code:sql} -- what was 'DEFAULT' is now 'LEGACY' CONTROL SET JOIN OPTIMIZER LEGACY; -- what was 'EXPERIMENTAL' is now 'STANDARD' CONTROL SET JOIN OPTIMIZER STANDARD; {code}
11858 Quoted identifiers can now contain dots. Error messages are improved to fully-qualify identifiers and use correct quoting. Adapter script schema and name are now separate columns in system tables for virtual schemas.
11369 Default behavior is unchanged. With the command line parameter "-zeroRawSizeForViewsAndScripts=1", views, scripts, and functions have 0 raw size.
9776 Fix a bug where the LEVEL, CONNECT_BY_ISCYCLE and CONNECT_BY_ISLEAF pseudocolumns for CONNECT BY could not be used when selecting from VALUES or VALUES BETWEEN.
2603 Column aliases are no longer ignored for emitting UDFs. If they are used on an emitting UDF that returns more than one value, Exasol throws an error.

New Features

Changelog Entry Summary
14526 Improvements for encrypted client connection handling (preview feature)
11680 Improvements for encrypted client connection handling

Improvements

Changelog Entry Summary
21276 ConfD job cert_update requires a certificate chain
19023 Improvements in the Compile Time
14248 JDBC: IMPORT/EXPORT LOCAL CSV/FBV: include file names of local files into auditing data
14199 Reduced compile time for queries with nested WITH clauses
14166 Improved storage fail safety
14035 Default activated auditing in new Exasol 8 deployments
14034 Database enforces encrypted connections
13966 Add JDBC and DRIVER as non-reserved keywords
13863 ODBC: Truncation of string values follows ODBC standards
13808 Improved Active Session Management for sessions with open read-only transactions
13751 IMPORT FROM JDBC: Allow sources without JDBC Connection.rollback() method
12517 Activation of new Join Order Optimizer by default
11858 Quoted identifiers can contain dot
11369 Raw size of scripts, views, and functions set to 0 bytes
9209 Smaller logfiles

Bug Fixes

Changelog Entry Summary
14664 Multiple references to VIEW or CTE containing an EMITS UDF return internal server error
14604 DML using system table within a subquery may cause exception
14569 COMMIT or ROLLBACK may hang
14568 LAG() in combination with IGNORE NULLS may return incorrect results
14506 The database may not recover from a crashed node
14430 Very strong filters on indexed columns may cause incorrect results
14371 Sustained very high load may cause database restart
14309 ODBC: SQLColAttribute returns wrong string length in case of truncation
14270 Client connections using TLS may be disconnected during log rotation
14225 Filter on rowid can return deleted rows
14197 Temporary UDF resources may not be cleaned up properly if the statement is stopped/killed
14195 IMPORT/EXPORT using JDBC may fail during log rotation
14096 ODBC and ADO.NET deactivates Snapshot Mode
14091 Metadata requests may cause a database restart in rare conditions
14065 Misleading durations of joins in query profiling
14045 Filters on Hashtype columns with a local index may fail
14029 RPC call may cause a database restart
13969 ODBC connection may fail when CONNECTTIMEOUT=0
13956 Generic internal server error reported instead of a session out of memory error
13930 DELETE with IN predicate containing expressions in WHERE clause may fail on empty tables
13796 SCALAR RETURN UDFs with large input and output data may produce wrong results
13768 Hanging query or logserver due to race conditions in communication layer
13727 TLS: Unexpected client disconnects may cause sessions and logins to hang in rare cases
13710 Incorrect results in filter evaluation for columns of type char() ascii and hash type
13676 Nodes may become/stay offline
13675 Internal server error when using a comparing column from outer subselect with scalar-joined subquery
13432 DML statements may not finish due to extremely rare race condition
13370 ALTER TABLE ADD COLUMN: missing length check for column name
13232 New optimizer: Wrong cardinality estimation for left joins
13228 ODBC: Character conversion and Data Direct driver manager
13056 Database fails to start after cluster enlargement due to exceeded schema raw size limits
12756 Denial of Service by attacker on the private network
12674 Automatic failover may not be triggered in very rare cases.
12476 Deadlock in log server may prevent updating auditing and statistics tables
11706 Exaoperation backup download interface inaccessible after restart
11313 ORDER BY with invalid syntax does not raise an error
10957 Crashed queries may be missing in EXA_DBA_AUDIT_SQL
9776 Missing LEVEL pseudo-column for VALUES and VALUES BETWEEN
7187 IMPORT FROM SCRIPT with table name instead of required column definition crashes
2603 Aliases for emitting UDFs are ignored