JDBC complex types return NULL arrays as empty arrays. For example, when executing this SQL statement:

=> SELECT ARRAY[null,ARRAY[1,2,3],null,ARRAY[4,5],null] as array;

The array column the server returns will be:

[[],[1,2,3],[],[4,5],[]]

Because of the null values in the string literal, it should return this value:

[null,[1,2,3],null,[4,5],null]

This is a work around to a limitation in Simba.

Under special circumstances, a sequence of statements to create and drop Python libraries fails. For example, the following session statements attempt to create Python libraries lib1 and lib2:

=> CREATE LIBRARY lib1 AS :lib1_path DEPENDS :numpy_path LANGUAGE 'Python';
=> DROP LIBRARY lib1;
=> CREATE LIBRARY lib2 AS :lib2_path DEPENDS :sklearn_path LANGUAGE 'Python';

Here, lib1 is a Python library that imports module numpy, while lib2 imports module sklearn, which relies on numpy. After lib1 is dropped, the CREATE LIBRARY statement for lib2 fails.

The Windows DSN configuration utility no longer sets vertica as the default KerberosServiceName value when editing a DSN.

Starting with version 11.1, providing a value causes the ODBC driver to assume the connection is using Kerberos authentication and communicates to the server that it prefers to use that authentication method, assuming that the user has a grant to a Kerberos authentication method. The KerberosServiceName value might be set in earlier versions of Windows ODBC DSNs. Clearing the value will resolve the issue. This issue only applies to users who have a Kerberos authentication method granted with a lower priority than other authentication methods and use the DSN configuration utility to set up a DSN on Windows.

Previously, when a Vertica node went down, the status of standby nodes in the [NODES|https://docs.vertica.com/latest/en/sql-reference/system-tables/v-catalog-schema/nodes/] system table could be shown as DOWN for a short period of time before switching back to STANDBY.

This has been fixed. The status of standby notes will now either remain on STANDBY or can be changed temporarily to UNKNOWN if Spread is disrupted for a long period of time.

A new view called statement_outcomes has been added. This view contains one record per session-statement describing the outcome: success/fail and, if the fail, then the reason behind it. For example, in case the INSERT query succeeds, but the subsequent related constraint check fails, the records for the statement will be success=false with the appropriate description in the "error" column.

The query_requests view has not changed. For example, an INSERT statement with a constraint check will have two records: success for the query and success for the related constraint check.

The new view is the consolidated statement view. For example, when it shows execution time for the statement, that includes the time of retries (if any happened).

In SQLTools Vertica driver versions 0.0.2 and later, the sessions table populates the following columns:

• client_pid
• client_type
• client_version
• client_os
• client_os_user_name
• client_os_hostname